[SERVER-41389] Pause the oplog visibility thread in mode SECONDARY Created: 30/May/19 Updated: 18/Nov/19 Resolved: 18/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Sprint: | Execution Team 2019-06-17, Execution Team 2019-11-04, Execution Team 2019-11-18 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
In secondary mode, secondary batch application logic already handles visibility and holes in the oplog. Both the in-memory oplogReadTimestamp and the persisted oplogTruncateAfterPoint are updated. There's no need for the oplog visibility thread to run and use resources doing unnecessary work. (plus it would get confusing with batch application unsetting the oplogTruncateAfterPoint while the oplog visibility thread keeps setting it) |