From 6db6a15cc1c3290a6097b8a329cd3118c74e42ec Mon Sep 17 00:00:00 2001 From: Elisey Zanko Date: Sun, 28 Jul 2019 11:44:44 +0500 Subject: [PATCH] Update Zookeeper documentation --- zookeeper/content.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zookeeper/content.md b/zookeeper/content.md index 8739eae66..1ee55f6e7 100644 --- a/zookeeper/content.md +++ b/zookeeper/content.md @@ -30,7 +30,7 @@ $ docker run -it --rm --link some-zookeeper:zookeeper zookeeper zkCli.sh -server ## %%STACK%% -This will start Zookeeper in [replicated mode](https://zookeeper.apache.org/doc/current/zookeeperStarted.html#sc_RunningReplicatedZooKeeper). Run `docker stack deploy -c stack.yml %%REPO%%` (or `docker-compose -f stack.yml up`) and wait for it to initialize completely. Ports `2181-2183` will be exposed. +This will start Zookeeper 3.5 in [replicated mode](https://zookeeper.apache.org/doc/current/zookeeperStarted.html#sc_RunningReplicatedZooKeeper). Please note, that Zookeeper 3.4 has slightly different `ZOO_SERVERS` format. Run `docker stack deploy -c stack.yml %%REPO%%` (or `docker-compose -f stack.yml up`) and wait for it to initialize completely. Ports `2181-2183` will be exposed. > Please be aware that setting up multiple servers on a single machine will not create any redundancy. If something were to happen which caused the machine to die, all of the zookeeper servers would be offline. Full redundancy requires that each server have its own machine. It must be a completely separate physical server. Multiple virtual machines on the same physical host are still vulnerable to the complete failure of that host.