You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jiangjie Qin (JIRA)" <ji...@apache.org> on 2017/10/09 18:59:00 UTC

[jira] [Created] (KAFKA-6029) Controller should wait for the leader migration to finish before ack a ControlledShutdownRequest

Jiangjie Qin created KAFKA-6029:
-----------------------------------

             Summary: Controller should wait for the leader migration to finish before ack a ControlledShutdownRequest
                 Key: KAFKA-6029
                 URL: https://issues.apache.org/jira/browse/KAFKA-6029
             Project: Kafka
          Issue Type: Improvement
          Components: controller, core
    Affects Versions: 1.0.0
            Reporter: Jiangjie Qin
             Fix For: 1.1.0


In the controlled shutdown process, the controller will return the ControlledShutdownResponse immediately after the state machine is updated. Because the LeaderAndIsrRequests and UpdateMetadataRequests may not have been successfully processed by the brokers, the leader migration and active ISR shrink may not have done when the shutting down broker proceeds to shut down. This will cause some of the leaders to take up to replica.lag.time.max.ms to kick the broker out of ISR. Meanwhile the produce purgatory size will grow.

Ideally, the controller should wait until all the LeaderAndIsrRequests and UpdateMetadataRequests has been acked before sending back the ControlledShutdownResponse.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)