Santosh Kumar Sahu created ZOOKEEPER-5062:
---------------------------------------------
Summary: Zookeeper cluster is non operational after DNS issue
while zk pod starting
Key: ZOOKEEPER-5062
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-5062
Project: ZooKeeper
Issue Type: Bug
Components: server
Affects Versions: 3.8.4
Environment: Check below pod logs for all 3 pods
[^zk-pod-0-logs.txt]
[^zk-pod-1logs.txt]
[^zk-pod-2logs.txt]
Reporter: Santosh Kumar Sahu
Attachments: zk-pod-0-logs.txt, zk-pod-1logs.txt, zk-pod-2logs.txt
We have deployed zookeeper 3.8.4 version in k8s in the form of statefulset.
We have 3 replicas and when we restart all pods simultaneously 3-4 times,
zookeeper cluster is down and no request is served.
Some DNS related logs get printed in one zk pod which keeps restarting
Below is the pod status
root@node-100-77-160-64:/home/mynamespace# kubectl get pod -n mynamespace -w |
grep zoo
cluster-p-zookeeper-0 1/1 Running
0 7m25s
cluster-p-zookeeper-1 0/1 Running
5 (36s ago) 7m26s
cluster-p-zookeeper-2 1/1 Running
0 7m26s
cluster-p-zookeeper-bragent-75d88ffc5-nft5l 1/1 Running
0 22h
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
