[
https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564012#comment-14564012
]
Joel Koshy commented on KAFKA-1367:
-----------------------------------
One minor issue with depending on the TMR for KAKFA-2225 even if we fix this is
that the consumer would need to periodically refresh its metadata in case the
ISR changes after it starts reading from a follower in ISR.
Another approach for KAFKA-2225 is to add the ISR information to the fetch
response. The followers will then have the current ISR information and so will
the consumers. There are at least two concerns though: first, it depends on a
live replica fetcher thread; second, it's a bit hacky to add ISR to fetch
response as it is more associated with metadata.
> 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)
