[SERVER-74598] Commands without explicit read concern could skip orphan filtering on secondaries Created: 03/Mar/23  Updated: 29/Oct/23  Resolved: 12/Jun/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2023-05-29, Sharding EMEA 2023-06-12
Participants:

 Description   

The ServiceEntryPoint relies on the presence of the "level" field in "readConcern" to check if shard versioning check is required on secondaries.
In case an external client didn't set the readConcern because they meant to use the default one (which is "local" since PM-1970) but the command doesn't permit implicit readConcern to be applied the command won't perform orphan filtering on secondary nodes.



 Comments   
Comment by Githook User [ 12/Jun/23 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-74598 Commands without explicit read concern could skip orphan filtering on secondaries
Branch: master
https://github.com/mongodb/mongo/commit/eb2aae414de5263dd665c53f1b77cd031714b9c9

Generated at Thu Feb 08 06:27:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.