You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2018/09/28 21:43:00 UTC
[jira] [Resolved] (KAFKA-6620) Documentation about "exactly_once"
doesn't mention "transaction.state.log.min.isr"
[ https://issues.apache.org/jira/browse/KAFKA-6620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guozhang Wang resolved KAFKA-6620.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.1.0
> Documentation about "exactly_once" doesn't mention "transaction.state.log.min.isr"
> -----------------------------------------------------------------------------------
>
> Key: KAFKA-6620
> URL: https://issues.apache.org/jira/browse/KAFKA-6620
> Project: Kafka
> Issue Type: Bug
> Components: documentation, streams
> Reporter: Daniel Qian
> Assignee: Lee Dongjin
> Priority: Major
> Fix For: 2.1.0
>
>
> Documentation about "processing.guarantee" says:
> {quote}The processing guarantee that should be used. Possible values are {{at_least_once}}(default) and {{exactly_once}}. Note that exactly-once processing requires a cluster of at least three brokers by default what is the recommended setting for production; *for development you can change this, by adjusting broker setting* `{color:#FF0000}*transaction.state.log.replication.factor*{color}`
> {quote}
> If one only set *transaction.state.log.replication.factor=1* but leave *transaction.state.log.min.isr* with default value (which is 2) the Streams Application will break.
> Hope you guys modify the doc, thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)