Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion modules/ROOT/pages/getting-started.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -235,11 +235,15 @@ If all has gone well then you will have successfully deployed a Stackable cluste

=== Apache ZooKeeper

We can test ZooKeeper by running the ZooKeeper CLI shell. The easiest way to do this is to run the CLI shell on the pod that is running ZooKeeper.
We can test ZooKeeper by running the ZooKeeper CLI shell. The easiest way to do this is to run the CLI shell on the pod that is running ZooKeeper. It might be necassary to determine and set the port.
Comment thread
csautter marked this conversation as resolved.
Outdated

[source,bash]
----
kubectl exec -i -t simple-zk-server-primary-0 -- bin/zkCli.sh
# optional, determine the port
PORT=$(kubectl get pod simple-zk-server-primary-0 -o=jsonpath='{.spec.containers[0].ports[0].containerPort}')
Comment thread
nightkr marked this conversation as resolved.
Outdated
echo $PORT
Comment thread
nightkr marked this conversation as resolved.
Outdated
kubectl exec -i -t simple-zk-server-primary-0 -- bin/zkCli.sh -server localhost:$PORT
Comment thread
csautter marked this conversation as resolved.
Outdated
----

The shell should connect automatically to the ZooKeeper server running on the pod. You can run the `ls /` command to see the list of znodes in the root path, which should include those created by Apache Kafka and Apache NiFi.
Expand Down
Loading