[
https://issues.apache.org/jira/browse/KAFKA-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056448#comment-14056448
]
Guozhang Wang commented on KAFKA-1530:
--------------------------------------
Hi Stanislav/Oleg,
Kafka server has a config called "controlled.shutdown.enable", and when it is
turned on, the shutting down process will first wait for all the leaders of the
current shutting down node to migrate to other nodes before shutting down the
server (http://kafka.apache.org/documentation.html#brokerconfigs).
For your first case, where the shutting down node is the only replica in ISR,
the shutting down process will block until there are other nodes back in ISR
and hence can take the partitions; for your second case where there are more
than one node in ISR, then it is guaranteed that the leaders of the shutting
down nodes will be moved to another ISR node.
> howto update continuously
> -------------------------
>
> Key: KAFKA-1530
> URL: https://issues.apache.org/jira/browse/KAFKA-1530
> Project: Kafka
> Issue Type: Wish
> Reporter: Stanislav Gilmulin
> Priority: Minor
> Labels: operating_manual, performance
>
> Hi,
>
> Could I ask you a question about the Kafka update procedure?
> Is there a way to update software, which doesn't require service interruption
> or lead to data losses?
> We can't stop message brokering during the update as we have a strict SLA.
>
> Best regards
> Stanislav Gilmulin
--
This message was sent by Atlassian JIRA
(v6.2#6252)
