Skip to content

Update getting-started.adoc - set zookeeper cli port #732

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: release/25.3
Choose a base branch
from
Open

Update getting-started.adoc - set zookeeper cli port #732

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4ac1d4d
Update getting-started.adoc
csautter Apr 17, 2025
dc8eda7
Update modules/ROOT/pages/getting-started.adoc
csautter Apr 26, 2025
a66761e
Update modules/ROOT/pages/getting-started.adoc
csautter Apr 26, 2025
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
View file
Open in desktop
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 necessary to determine and set the port.

[source,bash]
----
kubectl exec -i -t simple-zk-server-primary-0 -- bin/zkCli.sh
# optional, determine the port
Comment on lines +238 to +243
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't need to tell people to do the wrong thing first, might as well just do the correct thing immediately.

Suggested change
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 necessary to determine and set the port.
[source,bash]
----
kubectl exec -i -t simple-zk-server-primary-0 -- bin/zkCli.sh
# optional, determine the port
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.
[source,bash]
----

PORT=$(kubectl get pod simple-zk-server-primary-0 -o=jsonpath='{.spec.containers[0].ports[0].containerPort}')
Copy link
Member

@nightkr nightkr May 6, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm.. I don't think we should assume the order of the containers or ports. If we use jq we can decouple from that.

Suggested change
PORT=$(kubectl get pod simple-zk-server-primary-0 -o=jsonpath='{.spec.containers[0].ports[0].containerPort}')
PORT="$(kubectl get pod simple-zk-server-primary-0 -o=json | jq '.spec.containers[].ports[] | select(.name == "zk") | .containerPort')"

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, jq might be the better alternative. The idea was just to use the kubectl builtin features to keep it simple. If the order could change i would also prefer jq.

echo $PORT
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't think we need to print this out, to be honest.

Suggested change
echo $PORT

kubectl exec -i -t simple-zk-server-primary-0 -- bin/zkCli.sh -server "localhost:$PORT"
----

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