[
https://issues.apache.org/jira/browse/KAFKA-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058048#comment-14058048
]
Guozhang Wang commented on KAFKA-1530:
--------------------------------------
Hi Oleg,
If you are hitting KAFKA-1382 or KAFKA-1407, then the broker in trouble should
not either not leader or if it is the leader the other replica should be in
sync but just the leader cannot update the ISR in ZK because of the ZkVersion
bug. So it is OK to just hard kill the instance.
For your second question, I actually agree that this is an issue and we
currently do not have a solution (i.e. sth like a script) to keep the ordering
of the starting up so it may cause some data loss. Could you file a separate
JIra for this issue or you can just change the title/description of this ticket.
> howto update continuously
> -------------------------
>
> Key: KAFKA-1530
> URL: https://issues.apache.org/jira/browse/KAFKA-1530
> Project: Kafka
> Issue Type: Wish
> Reporter: Stanislav Gilmulin
> Assignee: Guozhang Wang
> 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)
