Details
-
Task
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
Sharding NYC
-
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
-
5
-
2
Description
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.