[
https://issues.apache.org/jira/browse/KAFKA-18060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17900011#comment-17900011
]
Chia-Ping Tsai commented on KAFKA-18060:
----------------------------------------
Maybe we can add following check to fix it.
// Supports the v0-v2 TxnOffsetCommitRequest
if (apiVersion <3 && isTransactional && memberEpoch ==
JoinGroupRequest.UNKNOWN_GENERATION_ID &&
memberId.equals(JoinGroupRequest.UNKNOWN_MEMBER_ID) &&
groupInstanceId == null)
return;
> new coordinator does not support v0-v2 TxnOffsetCommitRequest when using
> CONSUMER group
> ---------------------------------------------------------------------------------------
>
> Key: KAFKA-18060
> URL: https://issues.apache.org/jira/browse/KAFKA-18060
> Project: Kafka
> Issue Type: Bug
> Reporter: Chia-Ping Tsai
> Assignee: Chia-Ping Tsai
> Priority: Major
>
> TxnOffsetCommitRequest versions v0-v2 do not include a member ID, causing
> ConsumerGroup#validateOffsetCommit [0] to throw an UnknownMemberIdException.
> This prevents the old producer from calling sendOffsetsToTransaction.
> Note that TxnOffsetCommitRequest versions v0-v2 are included in KIP-896 [1],
> so it seems the new coordinator should support that operations
> [0]
> https://github.com/apache/kafka/blob/trunk/group-coordinator/src/main/java/org/apache/kafka/coordinator/group/modern/consumer/ConsumerGroup.java#L517
> [1]
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
