[
https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15233630#comment-15233630
]
Robert Christ edited comment on KAFKA-3042 at 4/9/16 6:53 PM:
--------------------------------------------------------------
Hi Flavio,
The logs can be found at:
https://s3-us-west-2.amazonaws.com/tivo-confluent/confluent.tar
Let me know if you have trouble accessing it. It does include the zookeeper
logs. We had just enabled the GC logs for zookeeper but it does cover the
period of the reproduction.
As for he zkCli.sh issue, I don't have a lot of information. I was watching
the kafka
logs and flipped back to my zkCli.sh session and it had disconnected and needed
to
reconnect. I do believe the session timed out and is probably the same root
cause
theat causes our kafka broker sessions to timeout.
was (Author: delbaeth):
Hi Flavio,
The logs can be found at:
https://s3-us-west-2.amazonaws.com/tivo-confluent/confluent.tar
Let me know if you have trouble accessing it. It does include the zookeeper
logs. We had just enabled the GC logs for zookeeper but it does cover the
period of the reproduction.
As for he zkCli.sh issue, I don't have a lot of information. I was watching
the kafka
logs and flipped back to my zkCli.sh session and it had disconnected and needed
to
reconnect. I do believe the session timed out and is probably the same root
cause
the causes our kafka broker sessions to timeout.
> 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)
