[
https://issues.apache.org/jira/browse/KAFKA-12557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Roesler resolved KAFKA-12557.
----------------------------------
Resolution: Fixed
> org.apache.kafka.clients.admin.KafkaAdminClientTest#testClientSideTimeoutAfterFailureToReceiveResponse
> intermittently hangs indefinitely
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-12557
> URL: https://issues.apache.org/jira/browse/KAFKA-12557
> Project: Kafka
> Issue Type: Bug
> Components: clients, core
> Reporter: John Roesler
> Assignee: John Roesler
> Priority: Major
> Fix For: 3.0.0, 2.8.0
>
>
> While running tests for [https://github.com/apache/kafka/pull/10397,] I got a
> test timeout under Java 8.
> I ran it locally via `./gradlew clean -PscalaVersion=2.12 :clients:unitTest
> --profile --no-daemon --continue
> -PtestLoggingEvents=started,passed,skipped,failed -PignoreFailures=true
> -PmaxTestRetries=1 -PmaxTestRetryFailures=5` (copied from the Jenkins log)
> and was able to determine that the hanging test is:
> org.apache.kafka.clients.admin.KafkaAdminClientTest#testClientSideTimeoutAfterFailureToReceiveResponse
> It's odd, but it hangs most times on my branch, and I haven't seen it hang on
> trunk, despite the fact that my PR doesn't touch the client or core code at
> all.
> Some debugging reveals that when the client is hanging, it's because the
> listTopics request is still sitting in its pendingRequests queue, and if I
> understand the test setup correctly, it would never be completed, since we
> will never advance time or queue up a metadata response for it.
> I figure a reasonable blanket response to this is just to make sure that the
> test harness will close the admin client eagerly instead of lazily.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
