[
https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14488218#comment-14488218
]
Jun Rao commented on KAFKA-1367:
--------------------------------
[~Skandragon], for the operational issue that you pointed out, there are jmx
such as the underReplicatedCount that one can leverage.
That said, it's probably useful for an admin client to know the accurate ISR.
As Guozhang has suggested, one approach is to register a watcher of the state
path for each partition. We probably need to do a bit experiments to see how
much overhead this adds. Another approach is to have the controller
periodically read the latest ISR for each partition. This is probably a bit
simpler to implement, but may not reflect ISR timely and may add unnecessary
load to ZK.
> 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++
> Fix For: 0.8.3
>
> 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)
