[SERVER-69050] Tenant oplog buffer collection may not get dropped after the migration is marked garbage collectable. Created: 22/Aug/22 Updated: 27/Oct/23 Resolved: 18/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | [DO NOT USE] Backlog - Server Serverless (Inactive) |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Serverless
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Assume, the recipient state doc is marked garbage collectable and majority replicated. Now a stepdown happens but before dropping the oplog buffer. Then, if a new primary steps up, there are chances, ttl can delete the expired state document before the POS machinery is able to read the state document and start the instance and drop the tenant oplog buffer collection. This can result in orphaned tenant oplog buffer collection which can be cleaned up later only by cloud intervention. |
| Comments |
| Comment by Suganthi Mani [ 18/Aug/23 ] |
| Comment by Didier Nadeau [ 18/Oct/22 ] |
|
suganthi.mani@mongodb.com steven.vannelli@mongodb.com should we close this ticket as "Gone away" given |
| Comment by Suganthi Mani [ 22/Aug/22 ] |
|
This is no longer problem after |