You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Francois Saint-Jacques (JIRA)" <ji...@apache.org> on 2015/02/06 22:35:35 UTC

[jira] [Commented] (KAFKA-1367) Broker topic metadata not kept in sync with ZooKeeper

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

Francois Saint-Jacques commented on KAFKA-1367:
-----------------------------------------------

Instead of silently removing the field, could the controller force a cache refresh on a metadata request?

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