[SERVER-44146] Instead of looking at 'local.oplog.' collections in the WiredTiger integration code only look for the single collection 'local.oplog.rs' Created: 22/Oct/19 Updated: 27/Oct/23 Resolved: 19/Jan/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dan Larkin-York |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Execution Team 2021-01-25 | ||||||||
| Participants: | |||||||||
| Description |
|
I suspect a lot can be cleaned up around this. E.g. there's a Namespace::oplog function, and WiredTigerKVEngine has a special counter _oplogManagerCounter to work around there being several local.oplog collections in order to start and stop the WiredTigerOplogManager once instead of several. |