Would you mind sharing your workaround with the community?
On Mon, Sep 15, 2014 at 10:17 PM, Bae, Jae Hyeon metac...@gmail.com wrote:
The above pull request didn't work perfectly. After a bunch of testing
experiment, we decided that fixing zkclient itself isn't easy. So we
decided to go with
I am not sure how many companies are running zookeeper like we are doing
and I haven't seen any other companies terminating all EC2 instances to
update zookeeper cluster. But in the worst case, zookeeper EC2 instances
can be replaced before restarting kafka broker and consumer, sharing the
Thanks for reporting this issue. Agree that this is a problem for Kafka
users using AWS. Please can you open a JIRA so we can keep track of this?
On Sun, Aug 17, 2014 at 11:41 AM, Bae, Jae Hyeon metac...@gmail.com wrote:
Recently, we found the serious ZkClient bug, actual Apache Zookeeper
The above pull request didn't work perfectly. After a bunch of testing
experiment, we decided that fixing zkclient itself isn't easy. So we
decided to go with another workaround.
We're expecting zookeeper 3.5.0 will be stabilized as soon as possible with
the feature to refresh connections and the
Recently, we found the serious ZkClient bug, actual Apache Zookeeper client
bug, which can bring down broker/consumer on zookeeper push.
We're running kafka and zookeeeper in AWS EC2 environment. Zookeeper
instances are bound with EIP to give the static hostname for each instance,
which means
