ShardingCatalogManager addShard() command should be forced to always use remote shard connection

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Sharding NYC 2022-04-04
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Andrew Shuvalov (Inactive)
            Reporter:
            Andrew Shuvalov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: