[
https://issues.apache.org/jira/browse/KAFKA-19352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17955478#comment-17955478
]
Chia-Ping Tsai commented on KAFKA-19352:
----------------------------------------
the root cause is traced by KAFKA-19357
To quickly fix this flaky issue, we can adopt the solution used by the old
framework—always creating the offset topic at the beginning. This eliminates
the 'no coordinator' error returned by the server when the offset topic doesn't
yet exist
> PlaintextConsumerCommitTest > testCommitAsyncCompletedBeforeConsumerCloses
> [1] Type=Raft-Isolated
> -------------------------------------------------------------------------------------------------
>
> Key: KAFKA-19352
> URL: https://issues.apache.org/jira/browse/KAFKA-19352
> Project: Kafka
> Issue Type: Test
> Components: clients, consumer
> Reporter: Bolin Lin
> Assignee: Chia-Ping Tsai
> Priority: Major
> Labels: client, flaky-test, integration-test
>
> happens in pr: [https://github.com/apache/kafka/pull/19807]
> PlaintextConsumerCommitTest > testCommitAsyncCompletedBeforeConsumerCloses
> [1] Type=Raft-Isolated,
> MetadataVersion=4.2-IV1,BrokerSecurityProtocol=PLAINTEXT,BrokerListenerName=ListenerName(EXTERNAL),ControllerSecurityProtocol=PLAINTEXT,ControllerListenerName=ListenerName(CONTROLLER)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
