add test to check that minOpTimeUpdaters is used to fetch latest opTime if shard fails during a migration

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • 3.3.11
    • Affects Version/s: 3.3.8
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 18 (08/05/16), Sharding 2016-08-29
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Suggested steps:

      1) Trigger a failpoint in migration before issuing the moveChunk.
      2) Restart the shard with recoverShardingState=false (this setParameter only affects if the minOpTimeRecovery document is used to recover sharding state) and without --shardsvr.
      3) Verify that minOpTimeUpdaters in the minOpTimeRecovery document is non-zero.
      3) Restart the shard with recoverShardingState=true and without --shardsvr.
      4) Verify that minOpTimeUpdaters in the minOpTimeRecovery document goes to zero.
      5) Verify that the (config)opTime in the recovery document has been updated.

              Assignee:
              Randolph Tan
              Reporter:
              Esha Maharishi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: