[
https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14654847#comment-14654847
]
Jiangjie Qin commented on KAFKA-1367:
-------------------------------------
[~ashishujjain] [~junrao] [~jjkoshy], I found some issue when trying to deploy
the latest trunk with this patch.
The problem is that during a rolling bounce in a cluster the ISR state
propagation flooded the controller to broker traffic, the controlled shutdown
of one broker takes about 1.5 hour to finish for a 30 node cluster.
Also, even during a clean cluster startup, there are more than 70,000 ISR
change ephemeral path got created.
I feel we need to either find another way to propagate ISR change other than
using zookeeper, or at very least we need to throttle the propagation rate to,
say, once every 10 seconds.
I'm going to create another ticket to address the issue. Hopefully the fix
should be quick. If the fix takes some time, do we consider reverting this
patch and rework on it?
> Broker topic metadata not kept in sync with ZooKeeper
> -----------------------------------------------------
>
> Key: KAFKA-1367
> URL: https://issues.apache.org/jira/browse/KAFKA-1367
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.0, 0.8.1
> Reporter: Ryan Berdeen
> Assignee: Ashish K Singh
> Labels: newbie++
> Fix For: 0.8.3
>
> Attachments: KAFKA-1367.patch, KAFKA-1367.txt,
> KAFKA-1367_2015-07-01_17:23:14.patch, KAFKA-1367_2015-07-06_22:04:06.patch
>
>
> When a broker is restarted, the topic metadata responses from the brokers
> will be incorrect (different from ZooKeeper) until a preferred replica leader
> election.
> In the metadata, it looks like leaders are correctly removed from the ISR
> when a broker disappears, but followers are not. Then, when a broker
> reappears, the ISR is never updated.
> I used a variation of the Vagrant setup created by Joe Stein to reproduce
> this with latest from the 0.8.1 branch:
> https://github.com/also/kafka/commit/dba36a503a5e22ea039df0f9852560b4fb1e067c
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
