-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Replication
I've spoke to benety.goh, and we believe the only users of this class are working with non-replicated collections, but if it were ever to be used with replicated collections, this lock acquisition is a bit suspect. Namely, it is not using AutoGetCollectionForRead even though it might perform reads. AutoGetCollectionForRead will ensure that a user's request for a readConcern of majority will be met, which maybe should happen here.
- related to
-
SERVER-25694 DocumentSourceCursor should destroy its PlanExecutor while holding the collection lock
- Closed