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

Test waits for state to change into SECONDARY after stepdown but it should wait for PRIMARY

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • ALL
    • Sharding 2020-01-27, Sharding 2020-02-10
    • 50

      Before doing a transaction this test steps down the primary node and waits until it becomes secondary, however, the router might not find out about that election so the following transaction fails with a noMaster error.

      The test should wait until the mongos finds a primary, something like this test

            Assignee:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Reporter:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: