You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-7Lines changed: 4 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -24,18 +24,13 @@ kubectl -n kafka get pvc
24
24
25
25
## Set up Zookeeper
26
26
27
-
The Kafka book (Definitive Guide, O'Reilly 2016) recommends that Kafka has its own Zookeeper cluster with at least 5 instances,
28
-
so we use the [official docker image](https://hub.docker.com/_/zookeeper/)
29
-
but with a [startup script change to guess node id from hostname](https://github.com/solsson/zookeeper-docker/commit/df9474f858ad548be8a365cb000a4dd2d2e3a217).
27
+
The Kafka book (Definitive Guide, O'Reilly 2016) recommends that Kafka has its own Zookeeper cluster with at least 5 instances.
28
+
We use the zookeeper build that comes with the Kafka distribution, and tweak the startup command to support StatefulSet.
30
29
31
30
```
32
31
kubectl create -f ./zookeeper/
33
32
```
34
33
35
-
Despite being a StatefulSet, there is no persistent volume by default.
36
-
If you lose your zookeeper cluster, kafka will be unaware that persisted topics exist.
37
-
The data is still there, but you need to re-create topics.
38
-
39
34
## Start Kafka
40
35
41
36
Assuming you have your PVCs `Bound`, or enabled automatic provisioning (see above), go ahead and:
@@ -85,4 +80,6 @@ Is the metrics system up and running?
0 commit comments