[ 
https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141749#comment-14141749
 ] 

Jun Rao commented on KAFKA-1367:
--------------------------------

Yes, in the current implementation, ISR returned from metadata requests can be 
inconsistent with what's stored in ZK. This is because metadata is only 
propagated from the controller to the brokers when the controller changes the 
leader or the ISR. However, when a follower catches up, the leader (not the 
controller) adds it back to ISR and updates ZK. That info is not propagated to 
all brokers.

Currently, the ISR part in a metadata response is not really used by the 
clients. Do you have a usage for this?

> 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)

Reply via email to