[SERVER-68850] In catalog shard POC, ShardingCatalogClientImpl should use only the remote client Created: 15/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 |
|
At this moment, ShardingCatalogClientImpl::getAllShards() is using local client as an exception when the cluster role is catalog shard. This is unclean. We should move the exception to bootstrap from the config.shards locally in the ShardRegistry. |