[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: |
|
||||||||||||||||||||
| 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 |
| 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 |