[
https://issues.apache.org/jira/browse/KAFKA-12574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17312389#comment-17312389
]
Ismael Juma commented on KAFKA-12574:
-------------------------------------
To clarify my last comment, I think it would have been less surprising if the
config had been deprecated for a few releases. But it doesn't look like we did
that:
{quote}"The processing guarantee that should be used. " +
"Possible values are <code>" + AT_LEAST_ONCE + "</code> (default), " +
"<code>" + EXACTLY_ONCE + "</code> (requires brokers version 0.11.0 or
higher), " +
"and <code>" + EXACTLY_ONCE_BETA + "</code> (requires brokers version 2.5 or
higher). " +
"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 " +
"<code>transaction.state.log.replication.factor</code> and
<code>transaction.state.log.min.isr</code>."
{quote}
> Deprecate eos-alpha
> -------------------
>
> Key: KAFKA-12574
> URL: https://issues.apache.org/jira/browse/KAFKA-12574
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: A. Sophie Blee-Goldman
> Priority: Blocker
> Labels: needs-kip
> Fix For: 3.0.0
>
>
> In KIP-447 we introduced a new thread-producer which is capable of
> exactly-once semantics across multiple tasks. The new mode of EOS, called
> eos-beta, is intended to eventually be the preferred processing mode for EOS
> as it improves the performance and scaling of partitions/tasks. The only
> downside is that it requires brokers to be on version 2.5+ in order to
> understand the latest APIs that are necessary for this thread-producer.
> We should consider deprecating the eos-alpha config, ie
> StreamsConfig.EXACTLY_ONCE, to encourage new. & existing EOS users to migrate
> to the new-and-improved processing mode, and upgrade their brokers if
> necessary.
> Eventually we would like to be able to remove the eos-alpha code paths from
> Streams as this will help to simplify the logic and reduce the processing
> mode branching. But since this will break client-broker compatibility, and
> 2.5 is still a relatively recent version, we probably can't actually remove
> eos-alpha in the near future
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
