-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: Backlog
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
-
Sharding EMEA 2021-05-03
If a ShardingDDLCoordinator throws an exception during its construction phase, before to actually persist its state document on disk, it will reach the onCompletion task and will try to delete its state document, since this document doesn't exists the PrimaryOnlyServiceOpObserver::onDelete() won't be triggered and the instance won't be released from the POS.
- is depended on by
-
SERVER-54905 Implement FSMs hierarchy testing concurrent DLL/CRUD/FCV operations
- Closed
-
SERVER-56555 Enable drop_collection_sharded.js FSM workload in stepdown suites
- Closed
-
SERVER-56557 Simplify create collection coordinator check phase
- Closed
- related to
-
SERVER-69835 Add functionality for PrimaryOnlyService for cleaning up instances
- Backlog
-
SERVER-61717 Ensure a POS instance remains in the POS map until the instance's run() is complete
- Open