[SERVER-68881] In Catalog shard POC, can load cluster id and version from local client Created: 16/Aug/22  Updated: 29/Oct/23  Resolved: 18/Aug/22

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

Type: Task Priority: Major - P3
Reporter: Andrew Shuvalov (Inactive) Assignee: Andrew Shuvalov (Inactive)
Resolution: Fixed Votes: 0
Labels: sharding-nyc-subteam2, sharding-nyc-subteam2-catalog-poc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2022-08-22
Participants:
Story Points: 2

 Description   

I experimented with disabling the ShardLocal, and it failed because it made the ShardingCatalogManager to make a remote call with local read concern. The code in head here.
Then it hits the invariant because ShardRemote requires majority read concern here. It's just another confirmation that the ShardingCatalogManager is designed to make all calls locally, we should not mix.

Another change is to convert the `PeriodicShardedIndexConsistencyChecker::_launchShardedIndexConsistencyChecker()` to do explicit local read.


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