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
I have created a zookeeper with replicas 3, and 3 pods successfully created by operator, and i have check the server with echo srvr |nc localhost 2181, the result indicates the cluster is ok ,with 2 follower and 1 leader.
and then, i change the replicas into 2, the pod-2 will terminate, and later the pod-1 will restarted.
the finally situation is cluster is not health, after check the pod-1's logs, the nc result not with imok, so the pod cannot ready.
and the cluster status indicates pod-1, is reatarting with log:
i have check the pod-0 with nc
server is not ready for handle request, the cluster is broken.
Importance
blocker
Location
(Where is the piece of code, package, or document affected by this issue?)
Suggestions for an improvement
(How do you suggest to fix or proceed with this issue?)
The text was updated successfully, but these errors were encountered:
I haven't check if that is intentionally but please keep in mind that it’s recommended that a ZooKeeper ensemble should have an odd number of machines in it. Quorum defines the rule to form a healthy Ensemble which is defined using a formula Q = 2N+1 where Q defines number of nodes required to form a healthy Ensemble which can allow N failure nodes.
Description
I have created a zookeeper with replicas 3, and 3 pods successfully created by operator, and i have check the server with
echo srvr |nc localhost 2181
, the result indicates the cluster is ok ,with 2 follower and 1 leader.and then, i change the replicas into 2, the pod-2 will terminate, and later the pod-1 will restarted.
the finally situation is cluster is not health, after check the pod-1's logs, the nc result not with imok, so the pod cannot ready.
and the cluster status indicates pod-1, is reatarting with log:
i have check the pod-0 with nc
server is not ready for handle request, the cluster is broken.
Importance
blocker
Location
(Where is the piece of code, package, or document affected by this issue?)
Suggestions for an improvement
(How do you suggest to fix or proceed with this issue?)
The text was updated successfully, but these errors were encountered: