kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Onur Karaman (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-6029) Controller should wait for the leader migration to finish before ack a ControlledShutdownRequest
Date Wed, 18 Oct 2017 18:41:01 GMT

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

Onur Karaman updated KAFKA-6029:
--------------------------------
    Issue Type: Sub-task  (was: Improvement)
        Parent: KAFKA-5027

> 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: Sub-task
>          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)

Mime
View raw message