[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260874#comment-16260874
]
Ismael Juma edited comment on KAFKA-5473 at 11/21/17 3:06 PM:
--------------------------------------------------------------
[~junrao] [~prasincs], I've closed a bunch of JIRAs as duplicates of this one
(and linked them) as I am hoping that the solution will handle all of the
issues related to zookeeper reconnection. Please take a quick look at the JIRAs
to verify.
was (Author: ijuma):
[~junrao] [~prasincs], I've closed a bunch of JIRAs as duplicates of this one
as I am hoping that the solution will handle all of the issues related to
zookeeper reconnection. Please take a quick look at the JIRAs to verify.
> handle ZK session expiration properly when a new session can't be established
> -----------------------------------------------------------------------------
>
> Key: KAFKA-5473
> URL: https://issues.apache.org/jira/browse/KAFKA-5473
> Project: Kafka
> Issue Type: Sub-task
> Affects Versions: 0.9.0.0
> Reporter: Jun Rao
> Assignee: Prasanna Gautam
> Fix For: 1.1.0
>
>
> In https://issues.apache.org/jira/browse/KAFKA-2405, we change the logic in
> handling ZK session expiration a bit. If a new ZK session can't be
> established after session expiration, we just log an error and continue.
> However, this can leave the broker in a bad state since it's up, but not
> registered from the controller's perspective. Replicas on this broker may
> never to be in sync.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
