[DOCS-4382] Automation cluster configuration: replicaSets elements can now take an optional "force" field Created: 18/Nov/14  Updated: 24/Feb/16  Resolved: 01/Apr/15

Status: Closed
Project: Documentation
Component/s: Cloud Manager
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Timothy Olsen (Inactive) Assignee: Bob Grabar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 9 years, 13 weeks, 1 day ago

 Description   

Each "replicaSets" element in the automation cluster configuration can now take an optional "force" field (haha) which itself takes an object with a required "currentVersion" field. If specified, automation will force a reconfiguration of the replica set if and only if the current version of the replica set configuration equals that specified by "currentVersion". This is useful if a replica set has lost a majority of its members and the user wants to reconfigure the replica without the lost members.

Example:

    "replicaSets": [
        {
            "_id": "rs1",
            "members": [
                {
                    "_id": 0,
                    "host": "bar"
                },
                {
                    "_id": 1,
                    "host": "baz"
                },
                {
                    "_id": 2,
                    "host": "foo",
                    "arbiterOnly" : true 
                }
            ],
             "force": { "currentVersion": 5 }
        }
    ],


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