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

Expose the commitment of the current config

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.4
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • Repl 2020-02-24, Repl 2020-03-09
    • 28

      In case safe config takes a long time to get committed, Atlas needs to retry and be able to poll the status of the current config in order to run the next reconfig command.

      Some options:
      1. Run the next reconfig anyway and get a ConfigurationInProgress error if the previous isn't committed yet.
      2. Add a dryRun option to reconifg, which only checks the commitment of the previous config without actually accepting the config.
      3. Report in the response of replSetGetConfig if a new option is present.
      4. Report the config status in replSetGetStatus.

            Assignee:
            jesse@mongodb.com A. Jesse Jiryu Davis
            Reporter:
            siyuan.zhou@mongodb.com Siyuan Zhou
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: