You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@brooklyn.apache.org by sj...@apache.org on 2015/10/14 15:55:57 UTC
[11/17] incubator-brooklyn git commit: add hot backup description to
docs
add hot backup description to docs
Project: http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/commit/ee7b43b2
Tree: http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/tree/ee7b43b2
Diff: http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/diff/ee7b43b2
Branch: refs/heads/master
Commit: ee7b43b2963258b204c9c6b4819c880532142872
Parents: 49eabd1
Author: Alex Heneveld <al...@cloudsoftcorp.com>
Authored: Tue Oct 13 10:28:58 2015 +0200
Committer: Alex Heneveld <al...@cloudsoftcorp.com>
Committed: Tue Oct 13 10:29:26 2015 +0200
----------------------------------------------------------------------
docs/guide/ops/high-availability.md | 5 +++++
1 file changed, 5 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/blob/ee7b43b2/docs/guide/ops/high-availability.md
----------------------------------------------------------------------
diff --git a/docs/guide/ops/high-availability.md b/docs/guide/ops/high-availability.md
index 2a2e512..5f05cca 100644
--- a/docs/guide/ops/high-availability.md
+++ b/docs/guide/ops/high-availability.md
@@ -21,6 +21,10 @@ Once one node is running as `MASTER`, other nodes start in either `STANDBY` or `
As with the standby node, if a hot-standby node detects that the master fails,
it will be a candidate for promotion to master.
+* In `HOT_BACKUP` mode, a Brooklyn instance will read and make available the live state of
+ entities, as a read-only copy. However this node is not able to become master,
+ so it can safely be used to test compatibility across different versions.
+
To explicitly specify what HA mode a node should be in, the following CLI options are available
for the parameter `--highAvailability`:
@@ -29,6 +33,7 @@ for the parameter `--highAvailability`:
* `master`: will startup as master; if there is already a master then fails immediately
* `standby`: will start up as lukewarm standby; if there is not already a master then fails immediately
* `hot_standby`: will start up as hot standby; if there is not already a master then fails immediately
+* `hot_backup`: will start up as hot backup; this can be done even if there is not already a master; this node will not be a master
The REST API offers live detection and control of the HA mode,
including setting priority to control which nodes will be promoted on master failure: