-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Sharding EMEA
-
Fully Compatible
-
ALL
-
Sharding EMEA 2023-04-03, Sharding EMEA 2023-04-17
-
135
This is problematic in a config catalog environment because CatalogClient::getCollection will perform a read with read concern majority with afterClusterTime against the config server. And since itself is the config server, it can get stuck waiting for the clusterTime since the node's opTime will not advance because it is still processing the collMod op, causing a cyclic dependency.
It is also not ideal that this call is performed while collection MODE_X is being held.
- is caused by
-
SERVER-68769 If a shard key index cannot be dropped then a user should not be able to hide that index
- Closed
-
SERVER-69429 Missing checks in collMod for shard key and unique index
- Closed
- is related to
-
SERVER-68769 If a shard key index cannot be dropped then a user should not be able to hide that index
- Closed