Github user tophei commented on the issue:
https://github.com/apache/zookeeper/pull/150
@anmolnar We have patched 451 into 3.4.12, and it worked in our setup so
far. Thanks for the advise.
---
Github user tophei commented on the issue:
https://github.com/apache/zookeeper/pull/150
@anmolnar Thanks for the comment. Actually I was trying to patch 451 into
release tag 3.4.10 too , but seems it has much conflicts. By the way, may patch
451 have additional changes that may have
Github user tophei commented on the issue:
https://github.com/apache/zookeeper/pull/150
@glasser Thanks for the sharing. Yeah, a static ip indeed would help work
around the issue. However, assign static ip to service in k8s seems to be a bit
heavy and less flexible when you need
Github user tophei commented on the issue:
https://github.com/apache/zookeeper/pull/150
We were recently run into this issue in cloud env.
Specifically, we have a kafka cluster setup in cloud, and it turns out to
be a failure when the zookeeper node is replaced, namely the ip
