[SERVER-65533] Operations with {readConcern:available} do not treat the collection as UNSHARDED Created: 13/Apr/22  Updated: 29/Oct/23  Resolved: 19/Apr/22

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 5.1.1, 5.2.1, 5.0.7
Fix Version/s: 5.0.8

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2022-04-18, Sharding EMEA 2022-05-02
Participants:

 Description   

The available read concern is supposed to be used for situations where there are partitions or unavailable nodes in a sharded cluster which prevent it from properly enforcing the required causality guarantees.

Because of this, we should be treating the collection as UNSHARDED.



 Comments   
Comment by Githook User [ 19/Apr/22 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-65533 Treat collection as UNSHARDED under

{readConcern:available}

Branch: v5.0
https://github.com/mongodb/mongo/commit/9f31cf68f4a62def8702c2885dc11eedb12d4b8b

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