You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Lucas Bradstreet (Jira)" <ji...@apache.org> on 2020/01/02 18:06:00 UTC

[jira] [Created] (KAFKA-9358) Explicitly resign controller leadership and broker znode

Lucas Bradstreet created KAFKA-9358:
---------------------------------------

             Summary: Explicitly resign controller leadership and broker znode
                 Key: KAFKA-9358
                 URL: https://issues.apache.org/jira/browse/KAFKA-9358
             Project: Kafka
          Issue Type: Improvement
          Components: controller, core
            Reporter: Lucas Bradstreet
            Assignee: Lucas Bradstreet


When shutting down the controller the broker shuts down the controller and then closes the zookeeper connection. Closing the zookeeper connection results in ephemeral nodes being removed. It is currently critical that the zkClient is closed after the controller is shutdown, otherwise a controller election will not occur if the broker being shutdown is currently the controller.

We should consider resigning leadership explicitly in the controller rather than relying on the zookeeper client being closed. This would ensure that any changes in shutdown order cannot lead to periods where a broker's controller component is stopped while also maintaining leadership until the zkClient is closed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)