[SERVER-53112] Replicated oplog buffer can fail while inserting documents on failover Created: 30/Nov/20 Updated: 29/Oct/23 Resolved: 15/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: | Jason Chan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-1791_milestone-D | ||
| 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, Repl 2020-12-28 | ||||||||
| Participants: | |||||||||
| Description |
|
Before Tenant Migration project(PM-1791), the oplog buffer used to be only unreplicated collection. But now, the oplog buffer can also be a replicated collection. A node step down/shutdown can make the buffer inserts to fail. But the oplog buffer assumes those inserts will always succeed. So, this fassert has to be replaced with uassert(). |
| Comments |
| Comment by Githook User [ 22/Jan/21 ] |
|
Author: {'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}Message: |
| Comment by Githook User [ 15/Dec/20 ] |
|
Author: {'name': 'Jason Chan', 'email': 'jason.chan@mongodb.com', 'username': 'jasonjhchan'}Message: |
| Comment by Suganthi Mani [ 30/Nov/20 ] |
|
+ I expect this ticket to make TenantMigrationRecipientService::Instance::_enqueueDocuments to forward oplog buffer insert errors to oplog fetcher. |