-
Type:
Bug
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: 4.2.0, 4.4.0
-
Component/s: Sharding
-
Catalog and Routing
-
ALL
-
Sharding EMEA 2023-10-16, Sharding EMEA 2023-10-30, CAR Team 2023-11-13, CAR Team 2023-11-27, CAR Team 2023-12-11, CAR Team 2023-12-25, CAR Team 2024-01-08, CAR Team 2024-01-22, CAR Team 2024-02-05, CAR Team 2024-02-19
-
3
This ticket is a specialization of SERVER-64730, to track this issue on 4.4 and 4.2 branches.
The forceShardFilteringMetadataRefresh method is the lowest-level shard version causality utility on the shards, whose purpose is to always move the shard version forward.
In versions 4.0 and earlier, it used to acquire collection X lock and check that the newly installed version is actually newer than the one on the CSS before installing it. Starting from version 4.2 though, as part of the transaction project it was changed to not acquire collection X-lock.
This means that two concurrent invocations of forceShardFilteringMetadataRefresh could potentially race with each other and install non-monotonous increasing versions (i.e., the shard version on a shard can go back in time).
- is caused by
-
SERVER-40258 Relax locking requirements for sharding metadata refresh on shards
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
SERVER-42838 A slow thread in forceShardFilteringMetadataRefresh can reset the shard's filtering metadata to UNSHARDED
-
- Closed
-