Wait lastStableRecoveryTimestamp to pass atClusterTime in resharding cloner

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Repl 2023-10-02, Repl 2023-10-16
    • 138
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We are now relying on the resumeToken to clone data, if the donor restarts in the middle and lastStableRecoveryTimestamp is smaller than the snapshot time we are reading, the donor will reconstruct the collection by reapplying oplogs, which will lead to a different physical layout and the resumeToken will point to something non-exist or wrong.

            Assignee:
            Jiawei Yang
            Reporter:
            Jiawei Yang
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: