[
https://issues.apache.org/jira/browse/KAFKA-5369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036785#comment-16036785
]
Rajini Sivaram commented on KAFKA-5369:
---------------------------------------
[~Koelli] Diagnostics were improved under KAFKA-5179. There is also a KIP open
to further improve this:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-152+-+Improve+diagnostics+for+SASL+authentication+failures.
> Producer hangs on metadata fetch from broker in security authorization
> related failures and no meaningful exception is thrown
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-5369
> URL: https://issues.apache.org/jira/browse/KAFKA-5369
> Project: Kafka
> Issue Type: Improvement
> Components: consumer, producer
> Affects Versions: 0.10.0.0
> Reporter: Koelli Mungee
>
> Debugging security related misconfigurations becomes painful since the only
> symptom is a hang trying to fetch the metadata on the producer side
> at java.lang.Object.wait(Native Method)
> at org.apache.kafka.clients.Metadata.awaitUpdate(Metadata.java:129)
> at
> org.apache.kafka.clients.producer.KafkaProducer.waitOnMetadata(KafkaProducer.java:528)
>
> at
> org.apache.kafka.clients.producer.KafkaProducer.doSend(KafkaProducer.java:441)
>
> at
> org.apache.kafka.clients.producer.KafkaProducer.send(KafkaProducer.java:430)
> at
> org.apache.kafka.clients.producer.KafkaProducer.send(KafkaProducer.java:353)
> There are no meaningful errors on the broker side either. Enabling
> Djavax.net.debug=all and/or Dsun.security.krb5.debug=true is an option,
> however this should be improved to get a meaningful error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
