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

Posted to dev@kafka.apache.org by "David Almroth (JIRA)" <ji...@apache.org> on 2013/03/09 16:43:13 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=13597981#comment-13597981 ] 

David Almroth commented on KAFKA-156:
-------------------------------------

This is feature is very important for me. I am intrested in migrating from Scribe to Kafka and this feature is the only thing keeping me from starting now. 

It looks like isse https://issues.apache.org/jira/browse/KAFKA-789 is a duplicate of this.

                
> 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
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira