[
https://issues.apache.org/jira/browse/KAFKA-20333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lianet Magrans resolved KAFKA-20333.
------------------------------------
Resolution: Fixed
> Flaky runCloseClassicConsumerMultiConsumerSessionTimeoutTest
> ------------------------------------------------------------
>
> Key: KAFKA-20333
> URL: https://issues.apache.org/jira/browse/KAFKA-20333
> Project: Kafka
> Issue Type: Test
> Components: clients, consumer
> Reporter: Lianet Magrans
> Assignee: Lianet Magrans
> Priority: Major
>
> Flaky in trunk lately.
> [https://develocity.apache.org/scans/tests?search.relativeStartTime=P28D&search.rootProjectNames=kafka&search.tags=trunk&search.timeZoneId=America%2FToronto&tests.container=org.apache.kafka.clients.consumer.PlaintextConsumerPollTest&tests.sortField=FLAKY&tests.test=runCloseClassicConsumerMultiConsumerSessionTimeoutTest()%5B1%5D]
> Logs show :
> [2026-03-16 13:28:44,969] WARN [Consumer clientId=consumer-test-group-65,
> groupId=test-group] consumer poll timeout has expired. This means the time
> between subsequent calls to poll() was longer than the configured
> max.poll.interval.ms, which typically implies that the poll loop is spending
> too much time processing messages. You can address this either by increasing
> max.poll.interval.ms or by reducing the maximum size of batches returned in
> poll() with max.poll.records.
> (org.apache.kafka.clients.consumer.internals.ConsumerCoordinator:1152)
>
> So this tells the max_poll_interval 100ms is too low. The test needs a
> max_poll_interval low enough so that when a consumer stops polling it
> eventually hit the poll timer expired and leaves, but not too low that the
> other stable consumers may get an expired poll-timer
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
