-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Serverless
-
Fully Compatible
-
ALL
-
Server Serverless 2023-03-20
When a recipient failover happens in the middle of tenant oplog application, we might resume applying those donor oplog entries from a point that was already applied due to the fact we first apply the donor oplog entries and then write no-op donor oplog entries for the given batch and we calculate the resume point by finding the latest no-op oplog entry . So, with the stricter mode 'kSecondary', re-applying those donor oplog entries can cause failure and leads to shard merge failure unnecessarily. So, change the tenant oplog application mode to kInitialSync (lenient mode)
- is related to
-
SERVER-72622 Resuming tenant oplog applier due to recipient failover can miss writing no-op entries for donor oplog entries.
- Closed