[DOCS-6160] Improve Cloud Manager error message when arbiter created with priority != 0 Created: 07/Sep/15  Updated: 11/Jan/17  Resolved: 17/Sep/15

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Improvement Priority: Minor - P4
Reporter: Eric Sommer Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 8 years, 22 weeks ago

 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).



 Comments   
Comment by Cailin Nelson [ 17/Sep/15 ]

This is an application generated error message, so a ticket in "Cloud Manager & Ops Manager Feature Requests" would be the right location.

Regardless, this validation has been removed from the application, so the request is no longer relevant.

Generated at Thu Feb 08 07:51:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.