Further investigation has uncovered a defect when resolving a hostname fails - https://issues.apache.org/jira/browse/KAFKA-8182
Looks like it has been present since support for resolving all DNS IPs was added. On Mon, 1 Apr 2019 at 15:55, Mark Anderson <manderso...@gmail.com> wrote: > Hi list, > > I've a question regarding a stack trace I see with the 2.2.0 consumer > > java.lang.IllegalStateException: No entry found for connection 0| > at > org.apache.kafka.clients.ClusterConnectionStates.nodeState(ClusterConnectionStates.java:339)| > at > org.apache.kafka.clients.ClusterConnectionStates.disconnected(ClusterConnectionStates.java:143)| > > at > org.apache.kafka.clients.NetworkClient.initiateConnect(NetworkClient.java:926)| > > at > org.apache.kafka.clients.NetworkClient.access$700(NetworkClient.java:67)| > at > org.apache.kafka.clients.NetworkClient$DefaultMetadataUpdater.maybeUpdate(NetworkClient.java:1090)| > > at > org.apache.kafka.clients.NetworkClient$DefaultMetadataUpdater.maybeUpdate(NetworkClient.java:976)| > > at org.apache.kafka.clients.NetworkClient.poll(NetworkClient.java:533)| > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:265)| > > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:236)| > > at > org.apache.kafka.clients.consumer.KafkaConsumer.pollForFetches(KafkaConsumer.java:1256)| > > at > org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:1200)| > at > org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:1176) > > From looking at the code in NetworkClient.initiateConnect I'm struggling > to see how the nodeConnectionId could have been removed from the connection > states between connecting call at line 917 and the exception being thrown > at line 926. Can anyone shed any light? > > Thanks, > Mark > > >
