-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding EMEA 2022-10-03, Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31, Sharding EMEA 2022-11-14, Sharding EMEA 2022-11-28, Sharding EMEA 2022-12-12, Sharding EMEA 2022-12-26, Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06
As part of the shard versioning protocol, we check if the shard version received is compatible with the current shard version of the shard we must also add the check for the index version component and add to the StaleConfigInfo information the received and wanted index version, so the caller can know if needs to:
- Do a refresh on the collection and chunks metadata
- Do a refresh on the index metadata
- Refresh both
We should also add checks to the service entry point and the scoped operation completion actions to prevent retrying after running onCollectionPlacementVersionMismatch if the index version is stale.
- depends on
-
SERVER-72479 Index version not properly parsed in shard role
- Closed
-
SERVER-70132 Handle FCV transitions for global indexes info
- Closed
-
SERVER-70795 Modify rename to update the index catalog metadata
- Closed
-
SERVER-70828 Modify resharding to update the index sharding catalog metadata
- Closed
-
SERVER-70922 Modify drop collection to clear the sharding index catalog
- Closed
- is depended on by
-
SERVER-72323 Improve the first refresh of a stale router by not getting the indexes by default
- Closed