Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 6.1.1, 5.0.14, 6.0.3, 6.2.0-rc0
Affects Version/s: None
Component/s: Query Execution
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v6.1, v6.0, v5.0
Sprint:
Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

Assignee:: Sergi Mateo Bellido
Reporter:: Sergi Mateo Bellido
Participants:: Garaudy Etienne, Githook User, Kyle Suarez, Sergi Mateo Bellido
Votes:: 0 Vote for this issue
Watchers:: 18 Start watching this issue

Created:: Oct 10 2022 06:58:32 AM UTC
Updated:: Oct 29 2023 09:32:09 PM UTC
Resolved:: Oct 26 2022 04:25:35 PM UTC
Confidence Status Last Update:: 13/Oct/22 3:48 PM