-
Type:
New Feature
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Server Programmability
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
Currently, instances are mainly released via the opObserver callback. However, there are cases when the PrimaryOnlyService instance can exist in the registry but with no corresponding document in the database. Users of PrimaryOnlyService will have to remember to call releaseInstance manually in these cases. The suggestion for this ticket is to provide a function that performs both deleting the state document and unconditionally releasing the instance to minize users from forgetting to release the instance manually.
- is related to
-
SERVER-56390 Failed to construct ShardingDDLCoordinators do not get released
-
- Closed
-
-
-
- Closed
-
-
SERVER-61717 Ensure a POS instance remains in the POS map until the instance's run() is complete
-
- Open
-