[SERVER-31032] Secondaries should default to 'available' read concern level when one is not specified Created: 11/Sep/17  Updated: 30/Oct/23  Resolved: 20/Sep/17

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-10838 Docs for SERVER-31032: Secondaries sh... Closed
Duplicate
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-10-02
Participants:

 Description   

Currently the 'shardVersion' of a request is only ignored when 'available' read concern is set in that request. So the default is 'local' read concern when none is specified. This is desirable on primaries, but we wish to maintain v3.4 behavior on secondaries by defaulting to 'available' when none is specified.

Update: the exception to a secondary request's default to 'available' read concern level is when afterClusterTime is specified without a level, in which case the default should be 'local'. As per SPEC-929.



 Comments   
Comment by Githook User [ 20/Sep/17 ]

Author:

{'email': 'dianna.hohensee@10gen.com', 'name': 'Dianna Hohensee', 'username': 'DiannaHohensee'}

Message: SERVER-31032 Make secondary requests default to 'available' rc-level when both rc-level and afterClusterTime are not specified
Branch: master
https://github.com/mongodb/mongo/commit/44a2de49607e5340efc7e84d265216723d403add

Generated at Thu Feb 08 04:25:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.