[KAFKA-16009] Fix PlaintextConsumerTest.testMaxPollIntervalMsDelayInRevocation

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.7.0
• Fix Version/s: 3.8.0
• Component/s: clients, consumer
• Labels: consumer-threading-refactor integration-tests timeout
• Assignee: Lucas Brutschy
• Reporter: Kirk True
• Created: 13/Dec/23 23:20
• Updated: 22/Feb/24 14:19
• Resolved: 19/Feb/24 14:34

Description

The integration test PlaintextConsumerTest.testMaxPollIntervalMsDelayInRevocation is failing when using the AsyncKafkaConsumer.

The error is:

org.opentest4j.AssertionFailedError: Timed out before expected rebalance completed
	at org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:38)
	at org.junit.jupiter.api.Assertions.fail(Assertions.java:134)
	at kafka.api.AbstractConsumerTest.awaitRebalance(AbstractConsumerTest.scala:317)
	at kafka.api.PlaintextConsumerTest.testMaxPollIntervalMsDelayInRevocation(PlaintextConsumerTest.scala:235)

The logs include this line:
 

[2023-12-13 15:20:27,824] WARN [Consumer clientId=ConsumerTestConsumer, groupId=my-test] 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.HeartbeatRequestManager:188)

 

I don't know if that's related or not.

 

 

Issue Links

• relates to: KAFKA-16104 Enable additional PlaintextConsumerTest tests for new consumer
• links to: GitHub Pull Request #15383