[
https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15233745#comment-15233745
]
James Cheng commented on KAFKA-3042:
------------------------------------
I was also connected using zkCli.sh at the same time and my connection also
hung. During that period, any keystrokes I entered into my zkCli.sh terminal
window didn't even echo back to me. After it finally errored out, all my
keystrokes finally come through, so I ended up with bunch of my "asdfasdf"
keystrokes on the screen. I don't remember if zkCli.sh exited (so I was at
bash) or just started paying attention again.
I think that zkCli.sh was by default negotiating a 30 second session timeout
with zookeeper. Rob, does that sound right?
> updateIsr should stop after failed several times due to zkVersion issue
> -----------------------------------------------------------------------
>
> Key: KAFKA-3042
> URL: https://issues.apache.org/jira/browse/KAFKA-3042
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.2.1
> Environment: jdk 1.7
> centos 6.4
> Reporter: Jiahongchao
> Attachments: controller.log, server.log.2016-03-23-01,
> state-change.log
>
>
> sometimes one broker may repeatly log
> "Cached zkVersion 54 not equal to that in zookeeper, skip updating ISR"
> I think this is because the broker consider itself as the leader in fact it's
> a follower.
> So after several failed tries, it need to find out who is the leader
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
