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

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

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.3.8
    • Fix Version/s: 3.3.11
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Sharding 18 (08/05/16), Sharding 2016-08-29
    • Linked BF Score:
      0

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              renctan Randolph Tan
              Reporter:
              esha.maharishi Esha Maharishi
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: