[SERVER-57103] Evaluate whether hello and auth should use implicit default read concern Created: 20/May/21  Updated: 10/Jun/21  Resolved: 10/Jun/21

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

Type: Task Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Samyukta Lanka
Resolution: Won't Fix Votes: 0
Labels: post-rc0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Repl 2021-05-31, Repl 2021-06-14
Participants:

 Description   

As part of this investigation, we should look into whether these commands should accept user defined read concern at all.



 Comments   
Comment by Samyukta Lanka [ 10/Jun/21 ]

After talking with blake.oler and shreyas.kalyan, we've concluded that hello/auth commands using read concern local is safe. Auth commands will only do reads on collections in the admin db (admin.system.users and maybe admin.system.roles). The admin db can't be sharded and live on the config servers (although copies can also exist on shards, which means that there is no worry about safe secondary reads or stale shard/database versions, which is the main concern when it comes to "local" vs "available" reads.

Closing this ticket as won't fix since these changes are unnecessary.

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