brooklyn-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [2/5] brooklyn-docs git commit: address PR comments
Date Tue, 14 Nov 2017 10:35:56 GMT
address PR comments


Branch: refs/heads/master
Commit: b48dae6759982140d77b76f828013779f73868c6
Parents: 20e497b
Author: Alex Heneveld <>
Authored: Mon Nov 6 23:41:10 2017 +0000
Committer: Alex Heneveld <>
Committed: Mon Nov 6 23:41:10 2017 +0000

 guide/blueprints/ | 7 +++----
 guide/blueprints/                | 5 ++++-
 2 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/guide/blueprints/ b/guide/blueprints/
index 603c331..b8b94fe 100644
--- a/guide/blueprints/
+++ b/guide/blueprints/
@@ -1,7 +1,6 @@
 There are a collection of policies, enrichers, and effectors to assist with common
-failover scenarios and more general anything which wants a primary elected and
+failover scenarios and more generally anything which requires the election and re-election
of a primary member.
 These can be used for:
@@ -48,7 +47,7 @@ The ElectPrimaryPolicy acts to keep exactly one of its children or members
as pr
 A simple use case is where we have two children, call them North and South, and we wish for
North to be primary.  If North fails, however, we want to promote and fail over to South.
 This can be done by:
 * adding this policy at the parent
-* setting ` ha.primary.weight` on North
+* setting `ha.primary.weight` on North
 * optionally defining `promote` on North and South (if action is required there to promote
 * observing the `primary` sensor to see which is primary
 * optionally setting `propagate.primary.sensor: main.uri` to publish `main.uri` from whichever
of North or South is active
@@ -63,7 +62,7 @@ If present, this will add the `PropagatePrimaryEnricher` enricher with those
 be propagated (but not effectors).
 For more sophisticated configuration, that enricher can be added and configured directly
-If no quorum.up or quorum.running is set on the entity, both will be set to a constant 1.
+If no `quorum.up` or `quorum.running` is set on the entity, both will be set to a constant
 #### ElectPrimary Effector
diff --git a/guide/blueprints/ b/guide/blueprints/
index 33fcde3..f34fdf3 100644
--- a/guide/blueprints/
+++ b/guide/blueprints/
@@ -87,7 +87,10 @@ example of this policy in use.
 - org.apache.brooklyn.policy.ha.ServiceFailureDetector
+The ServiceFailureDetector enricher detects problems and fires an `ha.entityFailed` (or other
configurable sensor)
+for use by ServiceRestarter and ServiceReplacer.
+The [introduction to policies]({{}}/start/ shows a worked 
+example of this in use.
 #### SshMachineFailureDetector Policy

View raw message