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

Expose the commitment of the current config

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.4
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Repl 2020-02-24, Repl 2020-03-09
    • Linked BF Score:
      28

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: