[SERVER-65105] ShardingCatalogManager addShard() command should be forced to always use remote shard connection Created: 31/Mar/22  Updated: 07/Apr/22  Resolved: 07/Apr/22

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

Type: Task Priority: Major - P3
Reporter: Andrew Shuvalov (Inactive) Assignee: Andrew Shuvalov (Inactive)
Resolution: Won't Do Votes: 0
Labels: sharding-nyc-subteam2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Sharding NYC 2022-04-04
Participants:

 Description   

In catalog shard implementation the ShardingCatalogManager::addShard() the Shard connection to the shard to be added should be always remote.

The reason for this is that in the catalog shard implementation the ShardingCatalogManager can run at the same server as the shard we are trying to add. The commands sent to that shard require majority concerns and probably other stuff not supported by a direct client. Just always force a remote shard connection by adding a shard registry createRemoteConnection() method.

For non catalog shard mode this is no-op because the shard is always remote.



 Comments   
Comment by Andrew Shuvalov (Inactive) [ 07/Apr/22 ]

Not needed

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