[SERVER-52934] Tenant oplog applier may not notify the waiters in TenantOplogApplier::_opTimeNotificationList. Created: 18/Nov/20 Updated: 29/Oct/23 Resolved: 02/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-11-30, Repl 2020-12-14 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 21 | ||||||||||||
| Description |
|
Currently, we schedule some tenant oplog applier cleanupwork (like transitioning the async component state to kComplete & notifying donor opTime waiters etc.,) on oplog applier executor. Since Tenant oplog applier uses scoped task-executor which can get shutdown during node shutdown and stepdown, these cleanup work may not get scheduled. This results in tenant oplog applier miss notifying the waiters in TenantOplogApplier::_opTimeNotificationList and another side-effect is that memory leak as this join can't happen. |
| Comments |
| Comment by Githook User [ 02/Dec/20 ] |
|
Author: {'name': 'Suganthi Mani', 'email': 'suganthi.mani@mongodb.com', 'username': 'smani87'}Message: |
| Comment by Githook User [ 02/Dec/20 ] |
|
Author: {'name': 'Suganthi Mani', 'email': 'suganthi.mani@mongodb.com', 'username': 'smani87'}Message: |
| Comment by Githook User [ 02/Dec/20 ] |
|
Author: {'name': 'Suganthi Mani', 'email': 'suganthi.mani@mongodb.com', 'username': 'smani87'}Message: |