[
https://issues.apache.org/jira/browse/KAFKA-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13946696#comment-13946696
]
Jay Kreps commented on KAFKA-1028:
----------------------------------
[~noslowerdna] This should theoretically make Kafka consistent and
non-available in the presence of network partitions. I wonder if it actually
does in practice? That is, if we run a cluster locally and subject it to
network partitions does it retain consistency? We could try this out using
Kyle's Jepsen stuff or (perhaps better) by adding coverage in the system test
framework so we run such a test regularly. Any chance you'd be up for trying
this out? It would make a good blog post...
> 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: Andrew Olson
> 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)
