-
Type: Task
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Sharding EMEA 2021-07-12
When acquiring a collection critical section, a "weak" reason is currently provided for DDL operations.
For example, the reason on rename participants simply includes the involved collections.
The objective of this ticket is to make the critical section reason more strict, requiring the inclusion in the reason of a unique identifier (e.g. the collection uuid) to avoid re-joining in case of bugs around similar operations.
This ticket is to address the problem both for recoverable and in-memory critical section, once SERVER-56788 will be completed.
- depends on
-
SERVER-56788 Extend the in-memory collection critical section to keep track of the ongoing operation
- Closed