[
https://issues.apache.org/jira/browse/KAFKA-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Olson updated KAFKA-1028:
--------------------------------
Attachment: KAFKA-1028.patch
Attaching patch for consideration.
Here's a summary of the new broker configuration properties included in this
patch.
replica.unclean.election.enable
Indicates whether to enable replicas not in the ISR set to be elected as leader
as a last resort, even though doing so may result in data loss.
default: true
replica.unclean.election.topics
Regular expression specifying override topics for which unclean leader election
is enabled; only applicable if replica.unclean.election.enable=false.
default value: ""
replica.clean.election.topics
Regular expression specifying override topics for which unclean leader election
is disabled; only applicable if replica.unclean.election.enable=true.
default value: ""
> 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
>
>
> 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.1.5#6160)
