You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jason Gustafson (Jira)" <ji...@apache.org> on 2020/04/01 22:29:00 UTC

[jira] [Created] (KAFKA-9802) Fix flaky system test `TransactionsTest.test_transactions`

Jason Gustafson created KAFKA-9802:
--------------------------------------

             Summary: Fix flaky system test `TransactionsTest.test_transactions`
                 Key: KAFKA-9802
                 URL: https://issues.apache.org/jira/browse/KAFKA-9802
             Project: Kafka
          Issue Type: Bug
            Reporter: Jason Gustafson
            Assignee: Jason Gustafson


Found when investigating a test failure in `kafkatest.tests.core.transactions_test.TransactionsTest.test_transactions`. The failure was caused by an unexpected transaction timeout. Looking into the logs, I found that the timeout was due to a Produce request which took just over 10s to complete. The test case that failed involved a hard kill of the broker, so it is certainly possible for some produce requests to reach up to the request timeout. 

The problem in this case is that `request.timeout.ms` was set to 30s while the `transaction.timeout.ms` was set to only 10s. There is no benefit to allowing a larger request timeout since the coordinator is just going to abort the transaction. So we should fix this test case to set these timeouts consistently. It might also be worth logging a warning to the user when the request timeout is larger than the transaction timeout.







--
This message was sent by Atlassian Jira
(v8.3.4#803005)