kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Cheng (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (KAFKA-1120) Controller could miss a broker state change
Date Fri, 09 Dec 2016 02:02:58 GMT

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

James Cheng edited comment on KAFKA-1120 at 12/9/16 2:02 AM:
-------------------------------------------------------------

Is KAFKA-4443 an instance of this? Should this closed because it is a duplicate, or are there
more instances of this that are not covered by KAFKA-4443?



was (Author: wushujames):
Is https://issues.apache.org/jira/browse/KAFKA-4443 an instance of this? Should this closed
because it is a duplicate, or are there more instances of this that are not covered by https://issues.apache.org/jira/browse/KAFKA-4443?


> Controller could miss a broker state change 
> --------------------------------------------
>
>                 Key: KAFKA-1120
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1120
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8.1
>            Reporter: Jun Rao
>              Labels: reliability
>
> When the controller is in the middle of processing a task (e.g., preferred leader election,
broker change), it holds a controller lock. During this time, a broker could have de-registered
and re-registered itself in ZK. After the controller finishes processing the current task,
it will start processing the logic in the broker change listener. However, it will see no
broker change and therefore won't do anything to the restarted broker. This broker will be
in a weird state since the controller doesn't inform it to become the leader of any partition.
Yet, the cached metadata in other brokers could still list that broker as the leader for some
partitions. Client requests routed to that broker will then get a TopicOrPartitionNotExistException.
This broker will continue to be in this bad state until it's restarted again.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message