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

Preserve shardedClusterCardinalityForDirectConns cluster parameter across magic restore

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The shardedClusterCardinalityForDirectConns parameter is used to determine if direct connections to a shard should be permitted. When we drop clusterParameters in the restore procedure, we lose this parameter value, causing a restored shard node to think it's the only shard in a cluster.

      When we drop the cluster parameters in magic restore, we should ensure to keep shardedClusterCardinalityForDirectConns. This ticket should also include a test with multiple shard nodes and authentication to ensure we cannot directly access a newly restored shard node directly.

            Assignee:
            Unassigned Unassigned
            Reporter:
            ali.mir@mongodb.com Ali Mir
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: