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

Make concurrency_sharded_initial_sync not run moveCollection

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • ClusterScalability Mar31-Apr14
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      This suite repeatedly turns one of the nodes on each shard from "secondary" state to "initial sync" state. While in "secondary" state, the node could end up getting targeted by the aggregate command from the ReshardingCollectionCloner which is a snapshot read at the cloneTimestamp. If the timestamp is less than the initial sync "defaultBeginFetchingOpTime", the command is expected to fail with IncompleteTransactionHistory and SnapshotTooOld (SERVER-87677). 

       

            Assignee:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Reporter:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: