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

Make awaitCloneTimestampChosen() robust

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • 0

      awaitCloneTimestampChosen() is used by resharding tests to ensure that the following command happens during the cloning/applying stage of the resharding operation. However, if the test does a command that is triggered by an internal thread(i.e. TTL monitor), it doesn't guarantee that the $clustertime on the donor was advanced and can't ensure that the timestamp of the next opolg entry is ahead of the chosen cloneTimestamp.

      Normally, the $clusterTime gossiping would cause the timestamp to advance on donors for the next command sent through the router. Call findOne() on the donors before returning from awaitCloneTimestampChosen() to make the function more robust. 

            Assignee:
            kruti.shah@mongodb.com Kruti Shah
            Reporter:
            kruti.shah@mongodb.com Kruti Shah
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: