Ensure replica set only node crashes when there is a configsvr/shardsvr primary

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • ALL
    • v8.1, v8.0, v7.0
    • Cluster Scalability 2024-4-1, Cluster Scalability 2024-4-15, Cluster Scalability 2024-4-29, Cluster Scalability 2024-5-13, Cluster Scalability 2024-5-27, Cluster Scalability 2024-6-10, Cluster Scalability 06/24/24, Cluster Scalability 2024-07-08, Cluster Scalability 2024-07-22
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The changes in SERVER-86328 added safety features to ensure that secondaries with cluster roles that do not match the primary's cluster role will crash. It does this by checking that the shard identity document replicated to the secondary matches its own cluster role, and if it doesn't it will crash. However, the code failed to account for a replica set only secondary and a configsvr/shardsvr primary.

            Assignee:
            Unassigned
            Reporter:
            Wenqin Ye
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: