From 44db686ef3996a57f9e714432f26d33d4ba93d3a Mon Sep 17 00:00:00 2001 From: Matthias Radestock Date: Fri, 18 Mar 2016 01:56:52 +0000 Subject: [PATCH] don't mention the election Fixes #2060. --- site/ipam/overview-init-ipam.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/site/ipam/overview-init-ipam.md b/site/ipam/overview-init-ipam.md index ce442f62..e01865a1 100644 --- a/site/ipam/overview-init-ipam.md +++ b/site/ipam/overview-init-ipam.md @@ -61,16 +61,16 @@ through three states: 'deferred', 'waiting' and 'achieved': themselves successfully * 'achieved' - consensus achieved; allocations proceed normally -Finally, some peers can be launched as election observers using the -`--observer` option: +Finally, some (but never all) peers can be launched as consensus +observers rather than participants by specifying the `--observer` +option: host4$ weave launch --observer $HOST3 -You do not need to specify an initial count to such peers, as they do -not participate in the election - they await its outcome. This can be -useful to add ephemeral peers to an existing fixed cluster (for example -in response to a scale-out event) without worrying about adjusting -initial peer counts accordingly. +You do not need to specify an initial peer count to such peers. This +can be useful to add ephemeral peers to an existing fixed cluster (for +example in response to a scale-out event) without worrying about +adjusting initial peer counts accordingly. #### `--init-peer-count` and How Quorum is Achieved @@ -152,4 +152,4 @@ to the rest of the network without any conflicts arising. * [Automatic Allocation Across Multiple Subnets](/site/ipam/allocation-multi-ipam.md) * [Plugin Command-line Arguments](/site/plugin/plug-in-command-line.md) - \ No newline at end of file +