[SERVER-86275] Investigate banning majority readConcern on sharding catalog access Created: 06/Feb/24  Updated: 07/Feb/24

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

Type: Improvement Priority: Major - P3
Reporter: Jordi Olivares Provencio Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Catalog and Routing
Participants:

 Description   

As part of SERVER-85869 we investigated the possibility of banning majority readConcern from the sharding catalog reads. This is a result of having seen multiple failures that had to be addressed due to reading faulty data.

One case is SERVER-54874 in which chunks were wrongly being read with majority readConcern, leading to invalid data being returned. Another is SERVER-75490 which had the same issue but now for the checkMetadataConsistency command.

Considering that the snapshot model is simpler to understand than majority reads we should investigate whether it makes sense to ban majority reads in favor of snapshot ones.


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