From fcead3aed94bc19e7ab2b5246484ae2670849783 Mon Sep 17 00:00:00 2001 From: Alexander Kukushkin Date: Wed, 15 Jul 2015 15:25:20 +0200 Subject: [PATCH] Update README.md --- README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 3ecbcebb..b894c5d9 100644 --- a/README.md +++ b/README.md @@ -55,8 +55,11 @@ For an example file, see `postgres0.yml`. Below is an explanation of settings: * *scope*: the relative path used on etcd's http api for this deployment, thus you can run multiple HA deployments from a single etcd * *session_timeout*: the TTL to acquire the leader lock. Think of it as the length of time before automatic failover process is initiated. * *reconnects_timeout*: how long we should try to reconnect to ZooKeeper after connection loss. After this timeout we assume that we don't have lock anymore and will restart in read-only mode. - * *hosts*: List of ZooKeeper cluster members in format: 'host1:port1,host2:port2,..etc...' - + * *hosts*: list of ZooKeeper cluster members in format: [ 'host1:port1', 'host2:port2', 'etc...'] + * *exhibitor*: if you are running ZooKeeper cluster under Exhibitor supervisory the following section could be interesting for you + * *poll_interval*: how often list of ZooKeeper and Exhibitor nodes should be updated from Exhibitor + * *port*: Exhibitor port + * *hosts*: initial list of Exhibitor (ZooKeeper) nodes in format: [ 'host1', 'host2', 'etc...' ]. This list would be updated automatically when Exhibitor (ZooKeeper) cluster topology changes. * *postgresql* * *name*: the name of the Postgres host, must be unique for the cluster