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

Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2016/10/05 09:30:21 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=15548193#comment-15548193 ] 

Ismael Juma commented on KAFKA-156:
-----------------------------------

To clarify, the issue where are tracking this is now https://issues.apache.org/jira/browse/KAFKA-1955 since it includes a WIP patch.

> 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
>            Assignee: Dru Panchal
>
> 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.3.4#6332)