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

More detailed config commitment status in replSetGetConfig

    • Type: Icon: New Feature New Feature
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Replication

      In SERVER-44812 we added commitmentStatus as a field in the replSetGetConfig reply. If the user passes commitmentStatus: true in the request, then the reply will also contain commitmentStatus, which is true iff the current replica set config has satisfied both of the "config commitment" checks:

      1. The current config has propagated to majority of the nodes in the current config
      2. The last optime written in the previous config has been replicated by a majority of nodes in the current config

      It could be useful to expose additional details. Specifically, we could add two more fields to replSetGetStatus, indicating whether condition 1 and/or condition 2 has been satisfied.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            jesse@mongodb.com A. Jesse Jiryu Davis
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: