[
https://issues.apache.org/jira/browse/KAFKA-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13948159#comment-13948159
]
Andrew Olson commented on KAFKA-1028:
-------------------------------------
The tests included with the patch do verify consistency and non-availability,
but they just shutdown and restart brokers rather than simulating a temporary
network partition. A few months ago I tried to get Jepsen+Kafka up and running,
without much success. I agree that a system test would be good to have. I'll
take a look at that framework to see how feasible it would be to add some tests
for this.
> 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)
