-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Cluster Scalability
-
Fully Compatible
-
v8.0, v7.3, v7.0
-
Sharding NYC 2023-08-21, Sharding NYC 2023-09-04, Sharding NYC 2023-09-18, Sharding NYC 2023-10-02, Sharding NYC 2023-10-16, Sharding NYC 2023-10-30, Cluster Scalability 2023-11-13, Cluster Scalability 2023-11-27, Cluster Scalability 2023-12-11, Cluster Scalability 2023-12-25, Cluster Scalability 2024-1-8, Cluster Scalability 2024-1-22, Cluster Scalability 2024-2-5, Cluster Scalability 2024-2-19, Cluster Scalability 2024-3-4, Cluster Scalability 2024-3-18, Cluster Scalability 2024-4-1, Cluster Scalability 2024-4-15, Cluster Scalability 2024-4-29, Cluster Scalability 2024-5-13, Cluster Scalability 2024-5-27, Cluster Scalability 2024-6-10, Cluster Scalability 06/24/24
-
200
-
2
Currently, if a client runs a command inside a session against a node right after it restarts, the command can fail clusterTime key validation with KeyNotFound if no majority committed snapshot was taken before the restart. Making KeysCollectionManager::getKeysForValidation() keep retrying the refresh if it fails with ReadConcernMajorityNotAvailableYet errors would allow such commands to succeed instead of failing with KeyNotFound errors.
- is related to
-
SERVER-91222 Make cluster_time_across_add_shard.js temporarily retry on KeyNotFound error after restarting the replica set
- Closed