Submitted a pull request: https://github.com/sgroschupf/zkclient/pull/24.
On Tue, Sep 24, 2013 at 1:46 PM, Neha Narkhede wrote:
> Ya, it is not very active, but you can submit patches to master on
> https://github.com/sgroschupf/zkclient
>
> Thanks,
> Neha
>
>
> On Tue, Sep 24, 2013 at 9:58 AM,
Ya, it is not very active, but you can submit patches to master on
https://github.com/sgroschupf/zkclient
Thanks,
Neha
On Tue, Sep 24, 2013 at 9:58 AM, Anatoly Fayngelerin wrote:
> That does sound like a saner solution. Which github repo do you submit
> patches to? It looks like the repo I post
That does sound like a saner solution. Which github repo do you submit
patches to? It looks like the repo I posted on originally(
https://github.com/sgroschupf/zkclient/issues/23) might be a little stale.
On Tue, Sep 24, 2013 at 11:34 AM, Neha Narkhede wrote:
> Thanks for explaining the bug. Thi
Thanks for explaining the bug. This is a serious issue that we should fix
at the zkclient level. We have submitted patches to them before and they
were pretty helpful in releasing a new version with the patch. I think that
will lead to a cleaner solution than trying to get around it in Kafka code
s
Joel - that is exactly right. ZkClient has no way to notify consumers of
this situation. The session end event gets fired, however, the session
begin event never occurs.
Neha - The issue manifested itself when producers were attempting to
discover topics/brokers. The kafka brokers had lost their Z
> node loss. Did the Kafka consumer not respond to rebalance events or did
> the server not respond to state change events ? Also, ephemeral nodes are
> lost only when sessions are expired on the zookeeper server or if clients
> close the session actively, how does losing connection lead to ephemer
For what it is worth I am currently looking into a problem that sounds
suspiciously related. We're seeing no node exceptions for the consumer node
during rebalance:
Caused by: org.apache.zookeeper.KeeperException$NoNodeException:
KeeperErrorCode = NoNode for
/consumers/es_consumer/ids/es_consu
Interesting. I haven't had the chance to dive into the zkclient codebase to
understand the root cause yet, but since you mentioned this can cause
ephemeral node loss, I am curious to know how you detected the ephemeral
node loss. Did the Kafka consumer not respond to rebalance events or did
the ser
