-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Fully Compatible
-
Sharding EMEA 2021-11-01, Sharding EMEA 2021-11-15, Sharding EMEA 2021-11-29, Sharding EMEA 2021-12-13, Sharding EMEA 2021-12-27, Sharding EMEA 2022-01-10, Sharding EMEA 2022-01-24, Sharding EMEA 2022-02-07, Sharding EMEA 2022-02-21, Sharding EMEA 2022-03-07, Sharding EMEA 2022-03-21, Sharding EMEA 2022-04-04, Sharding EMEA 2022-04-18, Sharding EMEA 2022-06-27
the usage of forceRefresh parameter has been removed in SERVER-46199 but there the parameter is still accepted by the SetShardVersion command. This ticket is to remove all the leftover traces of this parameter.
Moreover this if-else block should be removed and instead just call onShardVersionMismatch.
- depends on
-
SERVER-46199 Implement collection cache on top of ReadThroughCache to make it causally consistent
- Closed
-
SERVER-61072 Remove MigrationRecipientCriticalSection feature flag
- Closed
- related to
-
SERVER-47956 Get rid of the "authoritative" and "noConnectionVersioning" SSV parameters
- Closed