Skip to content

Commit 4ac1d4d

Browse files
authored
Update getting-started.adoc
1 parent 125edb3 commit 4ac1d4d

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

modules/ROOT/pages/getting-started.adoc

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -235,11 +235,15 @@ If all has gone well then you will have successfully deployed a Stackable cluste
235235

236236
=== Apache ZooKeeper
237237

238-
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.
238+
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.
239239

240240
[source,bash]
241241
----
242242
kubectl exec -i -t simple-zk-server-primary-0 -- bin/zkCli.sh
243+
# optional, determine the port
244+
PORT=$(kubectl get pod simple-zk-server-primary-0 -o=jsonpath='{.spec.containers[0].ports[0].containerPort}')
245+
echo $PORT
246+
kubectl exec -i -t simple-zk-server-primary-0 -- bin/zkCli.sh -server localhost:$PORT
243247
----
244248

245249
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.

0 commit comments

Comments
 (0)