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

moveChunk fails to complete after replSetReconfig

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Works as Designed
    • 2.7.6
    • None
    • Replication, Sharding
    • ALL
    • Hide

      The test is attached along with the log output.

      Basic steps are as follows:

      1. Configure 3 shard cluster with 3 node replica sets
      2. Create docs on sharded collection
      3. replSetReconfig on the toShard
      4. awaitReplication
      5. connPoolSync on mongos
      6. connPoolSync on primary toShard
      7. setShardVersion on primary toShard
      8. moveChunk

      Note: value of secondaryThrottle (true or false) does not affect behavior

      Show
      The test is attached along with the log output. Basic steps are as follows: Configure 3 shard cluster with 3 node replica sets Create docs on sharded collection replSetReconfig on the toShard awaitReplication connPoolSync on mongos connPoolSync on primary toShard setShardVersion on primary toShard moveChunk Note: value of secondaryThrottle (true or false) does not affect behavior

    Description

      The moveChunk command fails to complete after a replSetReconfig is issued on the toShard.

      Attachments

        1. move-ren2.log
          2.98 MB
          Jonathan Abrahams
        2. secondaryThrottle_moveChunk.js
          13 kB
          Jonathan Abrahams

        Issue Links

          Activity

            People

              randolph@mongodb.com Randolph Tan
              jonathan.abrahams Jonathan Abrahams
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: