Skip to content

Commit 6fa4caf

Browse files
31z4yosifkit
authored andcommitted
Enhance zookeeper documentation (#795)
* Enhance zookeeper documentation
1 parent a588bd1 commit 6fa4caf

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

zookeeper/content.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ This image includes `EXPOSE 2181 2888 3888` (the zookeeper client port, follower
2424

2525
## %%COMPOSE%%
2626

27-
This will start Zookeeper in [replicated mode](http://zookeeper.apache.org/doc/current/zookeeperStarted.html#sc_RunningReplicatedZooKeeper). Run `docker-compose up` and wait for it to initialize completely. Run `docker-compose ps` to figure out exposed ports.
27+
This will start Zookeeper in [replicated mode](http://zookeeper.apache.org/doc/current/zookeeperStarted.html#sc_RunningReplicatedZooKeeper). Run `docker-compose up` and wait for it to initialize completely. Ports `2181-2183` will be exposed.
2828

2929
> 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.
3030
@@ -76,4 +76,4 @@ This variable allows you to specify a list of machines of the Zookeeper ensemble
7676

7777
This image is configured with volumes at `/data` and `/datalog` to hold the Zookeeper in-memory database snapshots and the transaction log of updates to the database, respectively.
7878

79-
> Be careful where you put the transaction log. A dedicated transaction log device is key to consistent good performance. Putting the log on a busy device will adversely effect performance.
79+
> Be careful where you put the transaction log. A dedicated transaction log device is key to consistent good performance. Putting the log on a busy device will adversely affect performance.

zookeeper/docker-compose.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ services:
44
image: zookeeper
55
restart: always
66
ports:
7-
- 2181
7+
- 2181:2181
88
environment:
99
ZOO_MY_ID: 1
1010
ZOO_SERVERS: server.1=zoo1:2888:3888 server.2=zoo2:2888:3888 server.3=zoo3:2888:3888
@@ -13,7 +13,7 @@ services:
1313
image: zookeeper
1414
restart: always
1515
ports:
16-
- 2181
16+
- 2182:2181
1717
environment:
1818
ZOO_MY_ID: 2
1919
ZOO_SERVERS: server.1=zoo1:2888:3888 server.2=zoo2:2888:3888 server.3=zoo3:2888:3888
@@ -22,7 +22,7 @@ services:
2222
image: zookeeper
2323
restart: always
2424
ports:
25-
- 2181
25+
- 2183:2181
2626
environment:
2727
ZOO_MY_ID: 3
2828
ZOO_SERVERS: server.1=zoo1:2888:3888 server.2=zoo2:2888:3888 server.3=zoo3:2888:3888

0 commit comments

Comments
 (0)