[SERVER-50207] Investigate if ShardRegistry reads on configsvrs can always be majority Created: 10/Aug/20  Updated: 16/Jan/23  Resolved: 16/Jan/23

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

Type: Improvement Priority: Major - P3
Reporter: Kevin Pulo Assignee: Marcos José Grillo Ramirez
Resolution: Duplicate Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-64717 Shard registry is cleared during roll... Closed
Related
related to SERVER-46202 Implement ShardRegistry on top of Rea... Closed
is related to SERVER-64717 Shard registry is cleared during roll... Closed
Assigned Teams:
Sharding EMEA
Sprint: Sharding EMEA 2023-01-23
Participants:

 Description   

Apparently there are circumstances where the ShardRegistry on config servers sometimes reads non-majority-committed writes to config.shards, based on:

After SERVER-46202 makes the ShardRegistry causally consistent, it should be possible to eliminate any places where configsvrs do non-majority-commited ShardRegistry reads (thereby getting rid of ShardRegistry::clearEntries()).



 Comments   
Comment by Marcos José Grillo Ramirez [ 16/Jan/23 ]

All the instances have been removed, so marking this as a duplicate of SERVER-64717

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