[
https://issues.apache.org/jira/browse/KAFKA-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055437#comment-14055437
]
Guozhang Wang commented on KAFKA-1530:
--------------------------------------
Hi Stanislav,
Upgrading a kafka server does require bouncing it with the new jar, however if
you have a cluster of more than one server and data replication is turned on
(i.e. replication factor > 1 for all topics hosted) then this should not
interrupt the message brokering, since you will only bounce the brokers
sequentially and while one node is down, its brokering functionality will be
moved to other replicas.
The only exception is when you upgrade from 0.7 to 0.8.*, more details can be
found on this wiki:
https://cwiki.apache.org/confluence/display/KAFKA/Changes+in+Kafka+0.8
> 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)
