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

Recipient primary should wait on a different failpoint in tenant_migration_recipient_initial_sync_cloning.js

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.0.0-rc4, 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v5.0
    • Repl 2021-06-28
    • 53

      It is possible for an update to the stateDoc with rejectReadsBeforeTimestamp information to occur while the recipient primary is waiting on the failpoint right after data consistency. This should be changed so that the recipient primary cannot advance and lead to the failure of the following replSetStepUp command.

            Assignee:
            vishnu.kaushik@mongodb.com Vishnu Kaushik
            Reporter:
            vishnu.kaushik@mongodb.com Vishnu Kaushik
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: