Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-6160

Improve Cloud Manager error message when arbiter created with priority != 0

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Minor - P4 Minor - P4
    • 01112017-cleanup
    • None
    • None
    • None

    Description

      Example of current error message when arbiter not given priority 0:

      Invalid automation config: Replica Set _id: xxx member id: 3, host: yyy must have priority 0

      Error message could be clearer and also include the corrective action (click on the wrench on the right at the replica set level (same line as replica set name xxx) and change the priority of the arbiter node to 0).

      Attachments

        Activity

          People

            kay.kim@mongodb.com Kay Kim (Inactive)
            eric.sommer@mongodb.com Eric Sommer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              8 years, 22 weeks ago