[SERVER-53198] Tenant oplog applier doesn't commit the no-op writes which can make tenant migration to hang. Created: 02/Dec/20 Updated: 29/Oct/23 Resolved: 03/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | Suganthi Mani |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-1791_milestone-B | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Repl 2020-12-14 | ||||
| Participants: | |||||
| Linked BF Score: | 22 | ||||
| Description |
|
Currently, tenant oplog applier doesn't commit the no-op writes, but still forwarding the _lastAppliedOpTimesUpToLastBatch's recipient opTime. This can make the donor opTime waiters (recipientSyncData cmd) to hang indefinitely waiting on a recipient opTime that doesn't correspond to any oplog entry to be majority replicated. |
| Comments |
| Comment by Githook User [ 03/Dec/20 ] |
|
Author: {'name': 'Suganthi Mani', 'email': 'suganthi.mani@mongodb.com', 'username': 'smani87'}Message: |