FYI, DNS caching is still not fixed in 0.10. The zookeeper DNS cache has
been fixed for the zookeeper server where quorum members refresh the ip
address of their peers. But the client still doesn't do ip address refresh.
On Mon, Jan 9, 2017 at 9:56 PM, Jack Lund
wrote:
> On Thu, Jan 5, 2017 at 4
On Thu, Jan 5, 2017 at 4:32 PM James Cheng wrote:
>
> FYI, zookeeper 3.4.8 fixes the issue where you have to restart zookeeper
> nodes when their DNS mapping changes. I'm not sure how it affects
> restarting kafka though, when the zookeeper DNS changes.
>
> https://zookeeper.apache.org/doc/r3.4.8
> On Jan 5, 2017, at 7:55 AM, Jack Lund wrote:
>
> Hello, all.
>
> We're running multiple Kafka clusters in AWS, and thus multiple Zookeeper
> clusters as well. When we roll out changes to our zookeeper nodes (which
> involves changes to the AMI, which means terminating the zookeeper instance
>
Hello, all.
We're running multiple Kafka clusters in AWS, and thus multiple Zookeeper
clusters as well. When we roll out changes to our zookeeper nodes (which
involves changes to the AMI, which means terminating the zookeeper instance
and bringing up a new one in its place) we have to restart our
