[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:
Depends
depends on SERVER-47885 Have lookupCollectionBy{Namespace,UUI... Closed
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.


Generated at Thu Feb 08 05:05:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.