Yes, In case of UnknownHostException, zookeeper client will try to connect
remaining hostnames given in the zk connect string.
On Wed, Sep 26, 2018 at 7:45 PM James Yu wrote:
> @Liam, the hostname is removed from dns server due to the node is no longer
> alive, so kafka is unable reolve IP for
@Liam, the hostname is removed from dns server due to the node is no longer
alive, so kafka is unable reolve IP for zookeeper-2 thus an
NullPointerException is thrown.
@Manikumar, ZOOKEEPER-2184 is to re-resolve IP for new instance of
zookeeper-2, however, zookeeper-2 stays down hence now IP to be
You can try using Kafka 2.0 release. Original issue is handled in
ZOOKEEPER-2184 and corresponding
zookeeper version is used in Kafka 2.0.
On Wed, Sep 26, 2018 at 3:58 PM Liam Clarke
wrote:
> Hi James,
>
> That's not an unresponsive node that's killing Kafka, that's a failure to
> resolve the
Hi James,
That's not an unresponsive node that's killing Kafka, that's a failure to
resolve the address that's killing it - my personal expectation would be
that even though zookeeper-2.zookeeper.etc may be down, its name should
still resolve.
Regards,
Liam Clarke
On Wed, Sep 26, 2018 at
Hi,
I fail to start kafka broker when the corresponding zookeeper cluster is in
working but unhealthy state.
The zookeeper cluster is made of 3 nodes: zookeeper-0, zookeeper-1,
zookeeper-2.
I put all 3 zookeeper nodes into kafka's server.properties, specifically
for zookeeper.connect attribute
