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.
Recipient primary should wait on a different failpoint in tenant_migration_recipient_initial_sync_cloning.js
- Votes:
-
0 Vote for this issue
- Watchers:
-
1 Start watching this issue
- Created:
- Updated:
- Resolved: