[
https://issues.apache.org/jira/browse/KAFKA-10840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17784681#comment-17784681
]
Philip Nee commented on KAFKA-10840:
------------------------------------
Hey [~devin.bost] Are you still seeing this issue? I recently ran in to a
similar issue in Kafka Connect that the connector didn't catch the failed
authentication causing the task running for days on "Failed authentication with
...."
> Need way to catch auth issues in poll method of Java Kafka client
> -----------------------------------------------------------------
>
> Key: KAFKA-10840
> URL: https://issues.apache.org/jira/browse/KAFKA-10840
> Project: Kafka
> Issue Type: Improvement
> Reporter: Devin G. Bost
> Priority: Blocker
>
> We recently implemented SSL authentication at our company, and when certs
> expire, the Kafka client poll method silently fails without throwing any kind
> of exception. This is a problem because the data flow could stop at any time
> (due to certificate expiration) without us being able to handle it. The auth
> issue shows up in Kafka broker logs, but we don't see any indication on the
> client-side that there was an auth issue. As a consequence, the auth failure
> happens 10 times a second forever.
> We need a way to know on the client-side if an auth issue is blocking the
> connection to Kafka so we can handle the exception and refresh the certs
> (keystore/truststore) when the certs expire.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
