You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Steve Morin (JIRA)" <ji...@apache.org> on 2013/10/21 23:21:42 UTC

[jira] [Commented] (KAFKA-156) Messages should not be dropped when brokers are unavailable

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

Steve Morin commented on KAFKA-156:
-----------------------------------

Scott Carey - completely agree with your use-case here.  The ability todo rolling restarts and have processes spill to disk when there is outages so that we can in some-case withstand hours in stead of minutes in the case of a failure of the cluster or a strange network outage.

> Messages should not be dropped when brokers are unavailable
> -----------------------------------------------------------
>
>                 Key: KAFKA-156
>                 URL: https://issues.apache.org/jira/browse/KAFKA-156
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Sharad Agarwal
>             Fix For: 0.8.1
>
>
> When none of the broker is available, producer should spool the messages to disk and keep retrying for brokers to come back.
> This will also enable brokers upgrade/maintenance without message loss.



--
This message was sent by Atlassian JIRA
(v6.1#6144)