[SERVER-62664] Use explicit read concern in SessionsCollection Created: 14/Jan/22  Updated: 29/Oct/23  Resolved: 07/Jun/22

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

Type: Improvement Priority: Major - P3
Reporter: Gabriel Marks Assignee: Abdul Qadeer
Resolution: Fixed Votes: 0
Labels: neweng, sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-62214 Use explicit read concern in InitialS... Closed
related to SERVER-62713 Ensure internal readers set explicit ... Backlog
is related to SERVER-45692 Ensure all internal inter-node comman... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding NYC 2022-06-13
Participants:
Story Points: 2

 Description   

https://github.com/10gen/mongo/blob/6ff7c3a190cde6d3407fd5fae9006911a2216293/src/mongo/db/sessions_collection.cpp#L241 Here, we are using the implicit default read concern when we want to use read concern local. This is not ideal since the default read concern can be changed by the client. It would be better to use the local read concern explicitly here.



 Comments   
Comment by Githook User [ 07/Jun/22 ]

Author:

{'name': 'Abdul Qadeer', 'email': 'abdul.qadeer@mongodb.com', 'username': 'zorro786'}

Message: SERVER-62664 Change read concern in _doFindRemoved() to local from default
Branch: master
https://github.com/mongodb/mongo/commit/7ed710ca8dc4d4f65d2e8dc0eb625594bff8c3b4

Generated at Thu Feb 08 05:55:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.