Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-65105

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

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Sharding NYC 2022-04-04

    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.

      Attachments

        Activity

          People

            andrew.shuvalov@mongodb.com Andrew Shuvalov (Inactive)
            andrew.shuvalov@mongodb.com Andrew Shuvalov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: