[ 
https://issues.apache.org/jira/browse/KAFKA-17493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884641#comment-17884641
 ] 

David Jacot commented on KAFKA-17493:
-------------------------------------

[~ChrisEgerton] [~sagarrao] I looked into many of those failed tests with more 
logs and they were all due to pending members. It is basically similar to 
[https://github.com/apache/kafka/pull/16567.] There is no correctness issue, 
fortunately! However, I don't know why those would be flakier with the new 
coordinator. There does not seem to be a specific reason for it. I will 
continue to monitor it.

> Sink connector-related OffsetsApiIntegrationTest suite test cases failing 
> more frequently with new consumer/group coordinator
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-17493
>                 URL: https://issues.apache.org/jira/browse/KAFKA-17493
>             Project: Kafka
>          Issue Type: Test
>          Components: connect, consumer, group-coordinator
>            Reporter: Chris Egerton
>            Assignee: David Jacot
>            Priority: Major
>         Attachments: flaky-tests-gc.txt, passing-tests-gc.txt
>
>
> We recently updated trunk to use the new KIP-848 consumer/group coordinator 
> by default, which appears to have led to an uptick in flakiness for the 
> OffsetsApiIntegrationTest suite for Connect (specifically, the test cases 
> that use sink connectors, which makes sense since they're the type of 
> connector that uses a consumer group under the hood).
> Gradle Enterprise shows that in the week before that update was made, the 
> test suite had a flakiness rate of about 4% 
> (https://ge.apache.org/scans/tests?search.rootProjectNames=kafka&search.startTimeMax=1724558400000&search.startTimeMin=1723953600000&search.tags=trunk&search.timeZoneId=America%2FNew_York&tests.container=org.apache.kafka.connect.integration.*&tests.sortField=FLAKY),
>  and in the week and a half since, the flakiness rate has jumped to 17% 
> (https://ge.apache.org/scans/tests?search.rootProjectNames=kafka&search.startTimeMax=1725681599999&search.startTimeMin=1724731200000&search.tags=trunk&search.timeZoneId=America%2FNew_York&tests.container=org.apache.kafka.connect.integration.*&tests.sortField=FLAKY).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to