-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
(copied to CRM)
-
🟥 DDL
-
None
-
None
-
None
-
None
-
None
-
None
Similar to SERVER-117624 collMod can get stuck behind the long running index build while holding DDL lock. This creates a challenge as there are no means for the collMod interruption and stopping the index build can only be done via direct shard connection which is no longer available in v8.0+.
Can we consider that collMod should be smart enough to detect the index build and abort after a reasonable timeout instead of retrying indefinitely?
- is related to
-
SERVER-107819 Concurrent createIndex+collMod can leave behind inconsistent collection options
-
- Closed
-
-
SERVER-117624 Long running index builds may create temporary unavailability upon rename in sharded clusters
-
- Closed
-