[SERVER-85871] Don't signal oplog waiters under ReplicationCoordinator mutex Created: 29/Jan/24 Updated: 30/Jan/24 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
Something I noticed while analyzing work done under the ReplicationCoordinator mutex is that we signal all tailable oplog waiters while advancing the committed snapshot, which seems unnecessary and costly to do while holding the mutex. The CappedInsertNotifier already has its own mutex. |