This is an automated email from the ASF dual-hosted git repository. heneveld pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git
commit 46968f96e7053d380a4f3badf9552164bd72c8d1 Author: zan-mateusz <[email protected]> AuthorDate: Wed Nov 3 10:00:00 2021 +0000 minor changes as suggested --- guide/ops/high-availability/high-availability-supplemental.md | 2 +- guide/ops/high-availability/index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/guide/ops/high-availability/high-availability-supplemental.md b/guide/ops/high-availability/high-availability-supplemental.md index b67e853..a4b839e 100644 --- a/guide/ops/high-availability/high-availability-supplemental.md +++ b/guide/ops/high-availability/high-availability-supplemental.md @@ -68,7 +68,7 @@ This can be achieved via the `HA Status` table in the `About` page, which displa nodes in the current management plane. The control menu is opened by selecting the `Manage` option on the current server entry in the table. The following menu allows to change the priority value, as well as the status of the node. -- If a node is `MASTER`, it can demote itself by changing to another state. In such case, a new master will be selected from available standby servers, +- If a node is `MASTER`, it can demote itself by changing to another state. In such case, a new master is selected from available standby servers, basing on their priority. - If a node is `STANDBY`, or `HOT_STANDBY`, it can promote itself by changing to `MASTER` state. It is recommended for this server to have the highest priority amongst all available servers. diff --git a/guide/ops/high-availability/index.md b/guide/ops/high-availability/index.md index 2384a8f..e89cbcc 100644 --- a/guide/ops/high-availability/index.md +++ b/guide/ops/high-availability/index.md @@ -48,7 +48,7 @@ including setting priority to control which nodes will be promoted on master fai The High Availability management plane can also be controlled via the Brooklyn UI. More information is available in [`Configuraing HA - an example`](/guide/ops/high-availability/high-availability-supplemental.md) -Note that when POSTing to a non-master server it is necessary to pass a `Brooklyn-Allow-Non-Master-Access: true` header. +Note that when making a POST request to a non-master server it is necessary to pass a `Brooklyn-Allow-Non-Master-Access: true` header. For example, the following cURL command could be used to change the state of a `STANDBY` node on `localhost:8082` to `HOT_STANDBY`: curl -v -X POST -d mode=HOT_STANDBY -H "Brooklyn-Allow-Non-Master-Access: true" http://localhost:8082/v1/server/ha/state
