-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Query Execution
-
None
-
Fully Compatible
-
ALL
-
v6.1, v6.0, v5.0
-
Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31
The Sharding getOwnershipFilter 5.0 API requires the OperationShardingState to be versioned, otherwise it invariants. SERVER-52764 is the ticket that added back the invariant and in its description we were aware that we had to fix a usage in _internalSearchIdLookup stage, however we never did it (probably we thought that everything was fine because in a 5.0 deployment by default we didn't hit that invariant?).
In order to hit the invariant you have to set the read concern as available.
- is caused by
-
SERVER-52764 Reenable invariant that `getOwnershipFilter` should not be called without a valid shardVersion
- Closed
- related to
-
SERVER-70515 getShardFilterer utility doesn't fulfill some sharding preconditions
- Closed