Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Mon, 17 Mar 2014 23:46:44 +0000 (UTC)
From: "Jay Kreps (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.12665651.1377581759033.93431.1395100004880@arcas>
In-Reply-To: <JIRA.12665651.1377581759033@arcas>
References: <JIRA.12665651.1377581759033@arcas>
Subject: [jira] [Commented] (KAFKA-1028) per topic configuration of
 preference for consistency over availability
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jay Kreps commented on KAFKA-1028:
----------------------------------

No, I'm +1 too. Thanks Andrew!

> per topic configuration of preference for consistency over availability
> -----------------------------------------------------------------------
>
>                 Key: KAFKA-1028
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1028
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Scott Clasen
>            Assignee: Neha Narkhede
>         Attachments: KAFKA-1028.patch, KAFKA-1028_2014-01-30_13:45:30.patch, KAFKA-1028_2014-03-03_18:48:43.patch, KAFKA-1028_2014-03-17_09:39:05.patch
>
>
> As discussed with Neha on the ML.
> It should be possible to configure a topic to disallow unclean leader election, thus preventing the situation where committed messages can be discarded once a failed leader comes back online in a situation where it was the only ISR.
> This would open kafka to additional usecases where the possibility of committted messages being discarded is unacceptable.


--
This message was sent by Atlassian JIRA
(v6.2#6252)