Make replica set state changes take a write lock

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.2.4, 2.4.0-rc1
    • Affects Version/s: 2.2.3
    • Component/s: Replication
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      tryToGoLiveAsASecondary needs to take a write lock. Otherwise, we could become primary between lines 562 and 590 of rs_sync.cpp and then immediately become a secondary, not closing connections if anyone is syncing from us (which they may have been simply doing already through chained replication).

              Assignee:
              Kristina Chodorow (Inactive)
              Reporter:
              Kristina Chodorow (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: