[ 
https://issues.apache.org/jira/browse/KAFKA-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056422#comment-14056422
 ] 

Oleg edited comment on KAFKA-1530 at 7/9/14 4:33 PM:
-----------------------------------------------------

Another situation which happened in our production:
We have replication level 3. One out of 3 partition started lagging behind (due 
to network connectivity problems, etc.). Then while upgrading/restarting Kafka 
we restart the whole cluster. After upgrade the first node to start becomes a 
leader. It's highly likely it may be the lagging behind partition. Which in 
result leads to truncating two other partitions. In this case we loose data.

So we are seeking a mean of restarting/upgrading Kafka without data loose.


was (Author: ovgolovin):
Another situation which happened in our production:
We have replication level 3. One out of 3 partition started lagging behind (due 
to network connectivity problems, etc.). Then while upgrading/restarting Kafka 
we restart the whole cluster. After upgrade Kafka starts electing leaders for 
each partition. It's highly likely it may elect the lagging behind partition as 
a leader. Which in result leads to truncating two other partitions. In this 
case we loose data.

So we are seeking a means of restarting/upgrading Kafka without data loose.

> 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)

Reply via email to