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

when replica set member has full disk, step down to (sec|rec)?

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Diagnostics, Replication
    • Labels:
    • Environment:
      64-bit Linux, server 2.4.x, replica set
    • Replication

      When a replica has disk space issues it does not cause it to shut down, nor in the case of a primary, to step down. Instead the server periodically tests to see if enough space has been freed up to continue.

      As a result, the only indication of a problem is additional writes cause user asserts on the primary, and there's likely some introduction of repl lag on secondaries. But, from the perspective of rs.status() and db.serverStatus() everything looks fine (except for any introduced asserts/lag).

      Some options mentioned in discussion with server team:

      • Have replset member step down (if primary)
      • Have replset member enter maintenance status (until disk space is avail)
      • Add warning message to [startup]warning log

      Bonus: would be great if there was an explicit state/status change that could be picked up and reported by MMS. The last option should work for that.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            john.morales@mongodb.com John Morales (Inactive)
            Votes:
            10 Vote for this issue
            Watchers:
            18 Start watching this issue

              Created:
              Updated: