[
https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14581292#comment-14581292
]
Ashish K Singh commented on KAFKA-1367:
---------------------------------------
[~junrao] and [~jjkoshy], correct me if my understanding is wrong, but I think
we agreed on keeping ISR info in TMR and below mentioned approach is our
preference.
{quote}
When the leader changes the isr, in addition to writing the new isr in the
partition state in ZK, it also writes the change as a sequential node under a
new isrChangeNotification path in ZK. The controller listens to child changes
in the isrChangeNotification path. On child change, the controller reads the
new isr and broadcasts it through an UpdateMetadataRequest to every broker.
{quote}
Now that we want to keep ISR as part of TMR, do we still need a new
BrokerMetadataRequest?
> 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.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)
