[KAFKA-16010] Fix PlaintextConsumerTest.testMultiConsumerSessionTimeoutOnStopPolling

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: 3.7.0
• Component/s: clients, consumer
• Labels: consumer-threading-refactor integration-tests timeout
• Assignee: Lucas Brutschy
• Reporter: Kirk True
• Created: 13/Dec/23 23:27
• Updated: 09/Jul/24 12:12
• Resolved: 21/Feb/24 15:14

Description

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

The error is:

org.opentest4j.AssertionFailedError: Did not get valid assignment for partitions [topic1-2, topic1-4, topic-1, topic-0, topic1-5, topic1-1, topic1-0, topic1-3] after one consumer left
	at org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:38)
	at org.junit.jupiter.api.Assertions.fail(Assertions.java:134)
	at kafka.api.AbstractConsumerTest.validateGroupAssignment(AbstractConsumerTest.scala:286)
	at kafka.api.PlaintextConsumerTest.runMultiConsumerSessionTimeoutTest(PlaintextConsumerTest.scala:1883)
	at kafka.api.PlaintextConsumerTest.testMultiConsumerSessionTimeoutOnStopPolling(PlaintextConsumerTest.scala:1281)

The logs include these lines:
 

[2023-12-13 15:26:40,736] 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)
[2023-12-13 15:26:40,736] 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)
[2023-12-13 15:26:40,736] 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

• is duplicated by: KAFKA-15993 Enable max poll integration tests that depend on callback invocation
• relates to: KAFKA-16104 Enable additional PlaintextConsumerTest tests for new consumer