kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Json Tu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-4447) Controller resigned but it also acts as a controller for a long time
Date Fri, 25 Nov 2016 16:58:58 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Json Tu updated KAFKA-4447:
    Attachment: log.tar.gz

I upload the log's tar, we can unzip it using tar tools

> Controller resigned but it also acts as a controller for a long time 
> ---------------------------------------------------------------------
>                 Key: KAFKA-4447
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4447
>             Project: Kafka
>          Issue Type: Improvement
>          Components: controller
>    Affects Versions:,,,
>         Environment: Linux Os
>            Reporter: Json Tu
>         Attachments: log.tar.gz
> We have a cluster with 10 nodes´╝îand we execute following operation as below.
> 1.we execute some topic partition reassign from one node to other 9 nodes in the cluster,
and which triggered controller.
> 2.controller invoke PartitionsReassignedListener's handleDataChange and read all partition
reassign rules from the zk path, and executed all onPartitionReassignment for all partition
that match conditions.
> 3.but the controller is expired from zk, after what some nodes of 9 nodes also expired
from zk.
> 5.then controller invoke onControllerResignation to resigned as the controller.
> we found after the controller is resigned, it acts as controller for about 3 minutes,
which can be found in my attachment.

This message was sent by Atlassian JIRA

View raw message