kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Rosenberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-1028) per topic configuration of preference for consistency over availability
Date Sun, 03 Nov 2013 12:09:18 GMT

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

Jason Rosenberg commented on KAFKA-1028:

Agreed on a default setting.  Also, it would be nice if this could be configurable for topics
identified with a regex, so that all topics that match "*.reliable.*" will have this feature

Also, it would be good for it be applicable to existing topics, not only newly created ones,
so existing topics in a running system can have the benefit of this feature.

(In general too, default settings for topics identified via regex, and retroactive applicability,
are desirable for all per topic config  options).

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

View raw message