Details
-
Bug
-
Status: Reopened
-
Critical
-
Resolution: Unresolved
-
0.10.0.0, 2.4.1
-
None
-
jdk 1.7
centos 6.4
Description
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
Attachments
Attachments
Issue Links
- is duplicated by
-
KAFKA-3577 Partial cluster breakdown
- Resolved
- is related to
-
KAFKA-12405 Inconsistent broker without active topics still involved in coordinating consumer group
- Open
-
KAFKA-1407 Broker can not return to ISR because of BadVersionException
- Resolved
-
KAFKA-2729 Cached zkVersion not equal to that in zookeeper, broker not recovering.
- Resolved
-
KAFKA-1382 Update zkVersion on partition state update failures
- Closed
- relates to
-
KAFKA-3577 Partial cluster breakdown
- Resolved