[
https://issues.apache.org/jira/browse/KAFKA-10274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson reopened KAFKA-10274:
-------------------------------------
Apologies for the noise, but I'm going to reopen this. The recent fix addressed
the issue with the transaction timeout exceeding the wait time, but it also
opened the door again to the issue reported in KAFKA-9802.
> Transaction system test uses inconsistent timeouts
> --------------------------------------------------
>
> Key: KAFKA-10274
> URL: https://issues.apache.org/jira/browse/KAFKA-10274
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Major
>
> We've seen some failures in the transaction system test with errors like the
> following:
> {code}
> copier-1 : Message copier didn't make enough progress in 30s. Current
> progress: 0
> {code}
> Looking at the consumer logs, we see the following messages repeating over
> and over:
> {code}
> [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)
> {code}
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
