-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
27
Currently, there is no warranty that a collection state is not going to change after refreshing its filtering metadata and before acquiring the lock to cleanup the recover/refresh future.
The forceShardFilteringMetadataRefresh call should ideally be replaced by a method not acquiring locks, in order to not serialize other collection operations on it.
- depends on
-
SERVER-50627 Handle nested shard key fields in ShardVersionMap construction
- Closed