[KAFKA-10274] Transaction system test uses inconsistent timeouts

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.6.0
• Assignee: Jason Gustafson
• Reporter: Jason Gustafson
• Created: 14/Jul/20 23:16
• Updated: 22/Jul/20 19:11
• Resolved: 22/Jul/20 19:11

Description

We've seen some failures in the transaction system test with errors like the following:

copier-1 : Message copier didn't make enough progress in 30s. Current progress: 0

Looking at the consumer logs, we see the following messages repeating over and over:

[2020-07-14 06:50:21,466] DEBUG [Consumer clientId=consumer-transactions-test-consumer-group-1, groupId=transactions-test-consumer-group] Fetching committed offsets for partitions: [input-topic-1] (org.apache.kafka.clients.consumer.internals.ConsumerCoordinator)
[2020-07-14 06:50:21,468] DEBUG [Consumer clientId=consumer-transactions-test-consumer-group-1, groupId=transactions-test-consumer-group] Failed to fetch offset for partition input-topic-1: There are unstable offsets that need to be cleared. (org.apache.kafka.clients.consumer.internals.ConsumerCoordinator)

I think the problem is that the test implicitly depends on the transaction timeout which has been configured to 40s even though it expects progress after 30s.

Issue Links

• duplicates: KAFKA-10235 Fix flaky transactions_test.py
• links to: GitHub Pull Request #9026