Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Mon, 21 Oct 2013 21:21:42 +0000 (UTC)
From: "Steve Morin (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.12527292.1318685327943.99831.1382390502424@arcas>
In-Reply-To: <JIRA.12527292.1318685327943@arcas>
References: <JIRA.12527292.1318685327943@arcas>
Subject: [jira] [Commented] (KAFKA-156) Messages should not be dropped when
 brokers are unavailable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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