You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Antony Stubbs (JIRA)" <ji...@apache.org> on 2018/07/02 12:24:00 UTC

[jira] [Commented] (KAFKA-6268) Tools should not swallow exceptions like resolving network names

    [ https://issues.apache.org/jira/browse/KAFKA-6268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16529801#comment-16529801 ] 

Antony Stubbs commented on KAFKA-6268:
--------------------------------------

[~rsivaram] does this fix also cover security related errors like bad keystone passwords, can't obtain kerberos ticket, can't parse socket response (connected to wrong socket) type errors as well?

> Tools should not swallow exceptions like resolving network names
> ----------------------------------------------------------------
>
>                 Key: KAFKA-6268
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6268
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.11.0.1
>            Reporter: Antony Stubbs
>            Assignee: Stanislav Kozlovski
>            Priority: Major
>
> The cli consumer client shows nothing when it can't resolve a domain. This and other errors like it should be shown to the user by default. You have to turn on DEBUG level logging in the tools log4j to find there is an error.
> {{[2017-11-23 16:40:56,401] DEBUG Error connecting to node as-broker-1-eu-west-1b-public:9092 (id: 1 rack: null) (org.apache.kafka.clients.NetworkClient)
> java.io.IOException: Can't resolve address: as-broker-1-eu-west-1b-public:9092
> 	at org.apache.kafka.common.network.Selector.connect(Selector.java:195)
> 	at org.apache.kafka.clients.NetworkClient.initiateConnect(NetworkClient.java:764)
> 	at org.apache.kafka.clients.NetworkClient.access$600(NetworkClient.java:60)
> 	at org.apache.kafka.clients.NetworkClient$DefaultMetadataUpdater.maybeUpdate(NetworkClient.java:908)
> 	at org.apache.kafka.clients.NetworkClient$DefaultMetadataUpdater.maybeUpdate(NetworkClient.java:819)
> 	at org.apache.kafka.clients.NetworkClient.poll(NetworkClient.java:431)
> 	at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:232)
> 	at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:208)
> 	at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:199)
> 	at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.awaitMetadataUpdate(ConsumerNetworkClient.java:134)
> 	at org.apache.kafka.clients.consumer.internals.AbstractCoordinator.ensureCoordinatorReady(AbstractCoordinator.java:223)
> 	at org.apache.kafka.clients.consumer.internals.AbstractCoordinator.ensureCoordinatorReady(AbstractCoordinator.java:200)
> 	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.poll(ConsumerCoordinator.java:286)
> 	at org.apache.kafka.clients.consumer.KafkaConsumer.pollOnce(KafkaConsumer.java:1078)
> 	at org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:1043)
> 	at kafka.consumer.NewShinyConsumer.<init>(BaseConsumer.scala:64)
> 	at kafka.tools.ConsoleConsumer$.run(ConsoleConsumer.scala:72)
> 	at kafka.tools.ConsoleConsumer$.main(ConsoleConsumer.scala:53)
> 	at kafka.tools.ConsoleConsumer.main(ConsoleConsumer.scala)
> Caused by: java.nio.channels.UnresolvedAddressException
> 	at sun.nio.ch.Net.checkAddress(Net.java:101)
> 	at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:622)
> 	at org.apache.kafka.common.network.Selector.connect(Selector.java:192)
> 	... 18 more
> }}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)