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

Repl Members that are fsyncLock'd should not become primary

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
      None

      Description

      Repl Members that are fsyncLock'd should not become primary.

      Currently with SERVER-11103 being fixed, a replica set member which is SECONDARY and has been issued fsyncLock can become PRIMARY.

      From a high level, this seems counter productive, as we want the new primary available to take writes.

      Can we make it so that members which are under an fsyncLock block themselves from becoming primary.

      As part of this change, it may be worthwhile investigating the possibility of an indicator about fsyncLock within the output of rs.status() so end-users can isolate election problems with one command.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              david.hows David Hows
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: