[
https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15233564#comment-15233564
]
Flavio Junqueira commented on KAFKA-3042:
-----------------------------------------
[~delbaeth] thanks for all the information.
bq. Broker 1 rolled correctly and rejoined and leadership rebalancing
occurred. After broker 2 rolled and came back up it now has an inconsistent
view of the metadata. It thinks there are only 300 topics and all the other
brokers believe there are 700. Should we file this as a separate issue?
I'm not aware of this issue, so it does sound better to report it in a
different jira and describe the problem in as much detail as possible. If you
have logs for this problem, then please share.
bq. We have managed to reproduce the problem and have a snapshot of the logs.
The tarball is about a gigabyte. What should I do with it?
If you have a web server that can host it, then perhaps you can upload it
there. A dropbox/box/onedrive public folder that we can read from would also do
it.
bq. my zkCli.sh session which I was using to watch the controller exited here
so I was disconnected for a minute
This is odd. Could you describe in more detail what happened with the zkCli
session? You said that it disconnected for a minute, but has the session
expired? It must have expired, unless your session timeout was at least one
minute, which according to your description, it wasn't. If you have them,
please include the zk logs in the bundle.
> 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)
