Account for 1-node replica sets in getSecondaryHost

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • Fully Compatible
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-118560 added the first FSM concurrency suite to use a 1-node replica set (num_nodes: 1). Every other concurrency suite is either standalone, sharded, or a multi-node replica set — all of which getSecondaryHost() already handled. The new concurrency_with_mongot_extension_single_node suite exposed a latent edge case that had never been reachable before.

            Assignee:
            Daniel Segel
            Reporter:
            Daniel Segel
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: