-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v5.1
-
Server Serverless 2021-11-15, Server Serverless 2021-11-29
-
37
Since there are no writes on the donor during migration, the recipient can enter "consistent" before applying any oplog entries:
// If this optime has already passed, just return a ready future.
if (_lastAppliedOpTimesUpToLastBatch.donorOpTime >= donorOpTime ||
_beginApplyingAfterOpTime >= donorOpTime) {
return SemiFuture<OpTimePair>::makeReady(_lastAppliedOpTimesUpToLastBatch);
}
The tenant_migration_recipient_current_op.js test waits for the recipient to be "consistent" and asserts its currentOp's numOpsApplied is ≥ 1, which may be false if the recipient took this shortcut.
- is related to
-
SERVER-51246 Write a noop into the oplog buffer after each batch to ensure tenant applier reaches stop timestamp
-
- Closed
-
-
-
- Closed
-