Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-21531

Shard's connection blocks forever when attempting autosplit and first config server (SCCC) in TCP blackhole from shards

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.0-rc3
    • Component/s: Sharding
    • None
    • Sharding
    • ALL
    • Hide 
      python buildscripts/resmoke.py --executor sharding_legacy blackhole_first_config_server_from_shards_and_autosplit.js
      Show
      python buildscripts/resmoke.py --executor sharding_legacy blackhole_first_config_server_from_shards_and_autosplit.js
    • Sharding E (01/08/16)

      Tests the scenario when the first config server discards all messages from the shards, but not the mongos. Note that this prevents the autosplit from succeeding.

      1. Initialize the sharded cluster
      2. Enable sharding on the "test" database
      3. Create a sharded collection called "server16690" with shard key {_id: 1}
      4. Configure the mongobridge corresponding to the first config server to discard messages from each of the shards
      5. Insert a few documents into the test.server16690 collection to trigger an autosplit
      [js_test:blackhole_first_config_server_from_shards_and_autosplit] 2015-11-18T13:34:19.841-0500 d20010| 2015-11-18T13:34:19.840-0500 I SHARDING [conn7] received splitChunk request: { splitChunk: "test.server16690", keyPattern: { _id: 1.0 }, min: { _id: MinKey }, max: { _id: MaxKey }, from: "shard0000", splitKeys: [ { _id: ObjectId('564cc4ab70832ec51069b10c') }, { _id: ObjectId('564cc4ab70832ec51069b110') } ], configdb: "hanamizu:20015,hanamizu:20017,hanamizu:20019", shardVersion: [ Timestamp 1000|0, ObjectId('564cc4aba24c0213685f09d7') ], epoch: ObjectId('564cc4aba24c0213685f09d7') }
[js_test:blackhole_first_config_server_from_shards_and_autosplit] 2015-11-18T13:34:19.841-0500 d20010| 2015-11-18T13:34:19.840-0500 D SHARDING [conn7] created new distributed lock for test.server16690 on hanamizu:20015,hanamizu:20017,hanamizu:20019 ( lock timeout : 900000, ping interval : 30000, process : 0 )
[js_test:blackhole_first_config_server_from_shards_and_autosplit] 2015-11-18T13:34:19.841-0500 d20010| 2015-11-18T13:34:19.841-0500 D NETWORK  [conn7] creating new connection to:hanamizu:20015
[js_test:blackhole_first_config_server_from_shards_and_autosplit] 2015-11-18T13:34:19.842-0500 d20010| 2015-11-18T13:34:19.841-0500 D COMMAND  [ConnectBG] BackgroundJob starting: ConnectBG
[js_test:blackhole_first_config_server_from_shards_and_autosplit] 2015-11-18T13:34:19.842-0500 d20010| 2015-11-18T13:34:19.841-0500 D NETWORK  [conn7] connected to server hanamizu:20015 (127.0.1.1)
[js_test:blackhole_first_config_server_from_shards_and_autosplit] 2015-11-18T13:34:19.842-0500 b20015| 2015-11-18T13:34:19.841-0500 I NETWORK  [main] connection accepted from 127.0.0.1:41967 #14 (1 connection now open)
[js_test:blackhole_first_config_server_from_shards_and_autosplit] 2015-11-18T13:34:19.842-0500 b20015| 2015-11-18T13:34:19.841-0500 I BRIDGE   [thread1] Discarding "isMaster" command with arguments { isMaster: 1, hostInfo: "hanamizu:20010" } from hanamizu:20010

      This network request does not appear to time out, even after several minutes.

        1. blackhole_first_config_server_from_shards_and_autosplit.js
          1 kB
          Max Hirschhorn
        2. stacks.log
          63 kB
          Max Hirschhorn
        3. test_output.log
          1.28 MB
          Max Hirschhorn

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: