[
https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160538#comment-14160538
]
Guozhang Wang commented on KAFKA-1367:
--------------------------------------
Regarding the fix to this issue, we can either 1) remove the ISR field from the
metadata response and hence enforce people to use the admin tool (with ZK
dependency) for such usages, which would also require a protocol change between
client / server; or 2) let the controller to also watch for ISR change and
propagate that information to brokers, this will not introduce protocol change
to clients but will likely add a lot of burden on controllers since ISR change
is more frequent than leader migrations.
[~jjkoshy][~junrao] any other thoughts?
> 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
> Labels: newbie++
> Attachments: KAFKA-1367.txt
>
>
> 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)
