[
https://issues.apache.org/jira/browse/KAFKA-5792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765898#comment-16765898
]
Gert van Dijk edited comment on KAFKA-5792 at 2/12/19 8:28 PM:
---------------------------------------------------------------
I think I'm also seeing this issue still with 2.1.0 with my own AdminClient.
Reported via KAFKA-7924.
was (Author: gertvdijk):
I'm also seeing this issue still with 2.1.0 with my own AdminClient. It took me
huge amounts of time to figure out what is happening, to discover a unit test
is disabled in Kafka masking the erroneous behaviour. :(
FWIW, what I'm seeing with debug logging enabled is: 1) successful connection
to its bootstrap server. 2) huge amounts of those lines:
{noformat}
[kafka-admin-client-thread | adminclient-1] DEBUG
o.a.k.c.a.i.AdminMetadataManager - [AdminClient clientId=adminclient-1]
Updating cluster metadata to Cluster(id = q7XgghZqQUW_o5W2-Nn5Qw,
nodes = [], partitions = [], controller = null){noformat}
(note {{nodes = []}}.)
and 3) then, after a while (could be 1 second, could be 40+ seconds in my
case), it finally responds with a node and it connects just fine:
{noformat}
[kafka-admin-client-thread | adminclient-1] DEBUG
o.a.k.c.a.i.AdminMetadataManager - [AdminClient clientId=adminclient-1]
Updating cluster metadata to Cluster(id = q7XgghZqQUW_o5W2-Nn5Qw,
nodes = [kafka:9092 (id: 0 rack: null)], partitions = [],
controller = kafka:9092 (id: 0 rack: null))
[kafka-admin-client-thread | adminclient-1]
DEBUG o.apache.kafka.clients.NetworkClient -
[AdminClient clientId=adminclient-1] Initiating connection to node
kafka:9092 (id: 0 rack: null) using address kafka/xxxxx{noformat}
This all happens in a completely clean, freshly started, default configuration,
non-SSL, no-authentication, single-node Zookeeper-Kafka deployment in Docker
without any data or other connections. (See also [my QA @
ServerFault|https://serverfault.com/q/953393/135437].)
It would be really great if this could be fixed some day.
> Transient failure in KafkaAdminClientTest.testHandleTimeout
> -----------------------------------------------------------
>
> Key: KAFKA-5792
> URL: https://issues.apache.org/jira/browse/KAFKA-5792
> Project: Kafka
> Issue Type: Bug
> Reporter: Apurva Mehta
> Assignee: Colin P. McCabe
> Priority: Major
> Labels: transient-unit-test-failure
> Fix For: 2.2.0
>
>
> The {{KafkaAdminClientTest.testHandleTimeout}} test occasionally fails with
> the following:
> {noformat}
> java.util.concurrent.ExecutionException:
> org.apache.kafka.common.errors.TimeoutException: Timed out waiting for a node
> assignment.
> at
> org.apache.kafka.common.internals.KafkaFutureImpl.wrapAndThrow(KafkaFutureImpl.java:45)
> at
> org.apache.kafka.common.internals.KafkaFutureImpl.access$000(KafkaFutureImpl.java:32)
> at
> org.apache.kafka.common.internals.KafkaFutureImpl$SingleWaiter.await(KafkaFutureImpl.java:89)
> at
> org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:213)
> at
> org.apache.kafka.clients.admin.KafkaAdminClientTest.testHandleTimeout(KafkaAdminClientTest.java:356)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.kafka.common.errors.TimeoutException: Timed out waiting
> for a node assignment.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
