[
https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563960#comment-14563960
]
Joel Koshy commented on KAFKA-1367:
-----------------------------------
Jun - that is a good point. That sounds like a good approach to address the
concern with watcher counts. Another way is to just allow brokers to send an
equivalent update metadata (or similar) request to the controller to notify it
of an ISR change - or even allow leaders to broadcast update metadata requests
for ISR changes. We currently don't allow this, but maybe we should consider a
generic broker-broker communication component. Given the use-case that Theo
raised on the list yesterday, it appears we may want to keep the ISR even in
TMR v1. It may make sense to discuss this at an upcoming hangout especially
since it affects KIP-4.
> 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)
