[
https://issues.apache.org/jira/browse/KAFKA-18154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17903255#comment-17903255
]
TengYao Chi commented on KAFKA-18154:
-------------------------------------
I have looped the test and found some issues.
The root cause is that
`ShareConsumerTest#testMultipleConsumersInGroupFailureConcurrentConsumption`
might fail occasionally[0]. This failure can lead to consumer and producer
thread leaks. Since the consumer and producer are initiated by a thread pool,
the @AfterEach method only closes the admin and cluster but does not close the
thread pool, consumers, or producers.
As a result, the producer and consumer threads will attempt to reconnect to the
cluster indefinitely.
[0]
[0]https://github.com/apache/kafka/blob/e99561e1f30a30f9b151669a78d340f286a3ead6/core/src/test/java/kafka/test/api/ShareConsumerTest.java#L1253
> ShareConsumerTest suite times out sometimes
> -------------------------------------------
>
> Key: KAFKA-18154
> URL: https://issues.apache.org/jira/browse/KAFKA-18154
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Reporter: Lianet Magrans
> Assignee: TengYao Chi
> Priority: Major
>
> Got timeout on PR build due to ShareConsumerTest, timing out on
> destroyCluster that runs after each test (unrelated PR, with client changes
> for validations while building ConsumerGroupHeartbeat request)
> [https://github.com/apache/kafka/actions/runs/12146890124/job/33872229281?pr=17989]
> Running the suite locally on trunk takes around 12mins (and the current
> specified timeout is 20 mins).
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
