[v4.4] shard_aware_init_secondaries.js does not wait for replica set to stabilize

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Cluster Scalability
    • ALL
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This test restarts the secondary.

      As a result, the primary doesn't see the secondary for a few seconds. Therefore, when the test ends and we call stopSet, the primary is prone to stepping down. If it does step down, it can cause problems when we are trying to freeze and validate the replica set.

            Assignee:
            [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            Vishnu Kaushik
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: