[
https://issues.apache.org/jira/browse/KAFKA-9451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17025464#comment-17025464
]
ASF GitHub Bot commented on KAFKA-9451:
---------------------------------------
mjsax commented on pull request #8014: KAFKA-9451: Pass group metadata into
producer in Kafka Streams
URL: https://github.com/apache/kafka/pull/8014
**DO NOT MERGE**
Follow up to #7977 (note that the first commit is the squashed version of
7977; this commits need to be rebased after 7977 is merged).
Second commit (still need to add tests):
Part of KIP-447: when EOS is enabled in Kafka Streams, we need to pass the
consumer's group metadata into the producer to use the new GroupCoordinator
fencing mechanism.
We also need to first commit all task individually before we commit the
transaction or write the local checkpoint file.
During an upgrade, we will still use a producer per task (and rely on
transactional fencing), however, we will already pass the metadata to the
producer to enable GroupCoordinator fencing (in parallel to transactional
fencing), to prepare for a second round of rebalancing that switches to the
thread producer model and thus disables transactional fencing.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Pass consumer group metadata to producer on commit
> --------------------------------------------------
>
> Key: KAFKA-9451
> URL: https://issues.apache.org/jira/browse/KAFKA-9451
> Project: Kafka
> Issue Type: Sub-task
> Components: streams
> Reporter: Matthias J. Sax
> Assignee: Matthias J. Sax
> Priority: Major
>
> Using producer per thread EOS design, we need to pass the consumer group
> metadata into `producer.sendOffsetsToTransaction()` to use the new consumer
> group coordinator fenchning mechanism. We should also reduce the default
> transaction timeout to 10 seconds (compare the KIP for details).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
