-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
ALL
-
CAR Team 2024-03-04
-
156
With SERVER-85869 we made it so that shard registry reads would exclusively use snapshot readConcern. However, in a mixed version cluster with 5.0 and 4.4 the operation will fail as snapshot reads outside of a transaction weren't supported there.
As a result we should make the operation retry the operation with majority reads if it receives an InvalidOptions error.
- is caused by
-
SERVER-85869 Exhaustive find on config shard can return stale data
- Closed