You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Boyang Chen (Jira)" <ji...@apache.org> on 2020/05/05 05:56:00 UTC

[jira] [Resolved] (KAFKA-8587) One producer per thread for Kafka Streams EOS

     [ https://issues.apache.org/jira/browse/KAFKA-8587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Boyang Chen resolved KAFKA-8587.
--------------------------------
    Resolution: Fixed

> One producer per thread for Kafka Streams EOS
> ---------------------------------------------
>
>                 Key: KAFKA-8587
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8587
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Boyang Chen
>            Assignee: Boyang Chen
>            Priority: Major
>
> Currently exactly-once producer is coupled with individual input partitions. This is not a well scaled solution for client application such as Kafka Streams, and the root cause is that EOS producer doesn't understand the topic partition move throughout consumer group rebalance. By amending this semantic gap, we could achieve much better EOS scalability.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)