You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "radai rosenblatt (JIRA)" <ji...@apache.org> on 2018/10/11 14:59:00 UTC

[jira] [Resolved] (KAFKA-7475) print the actual cluster bootstrap address on authentication failures

     [ https://issues.apache.org/jira/browse/KAFKA-7475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

radai rosenblatt resolved KAFKA-7475.
-------------------------------------
       Resolution: Fixed
         Reviewer: Rajini Sivaram
    Fix Version/s: 2.1.0

> print the actual cluster bootstrap address on authentication failures
> ---------------------------------------------------------------------
>
>                 Key: KAFKA-7475
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7475
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: radai rosenblatt
>            Assignee: radai rosenblatt
>            Priority: Major
>             Fix For: 2.1.0
>
>
> currently when a kafka client fails to connect to a cluster, users see something like this:
> {code}
> Connection to node -1 terminated during authentication. This may indicate that authentication failed due to invalid credentials. 
> {code}
> that log line is mostly useless in identifying which (of potentially many) kafka client is having issues and what kafka cluster is it having issues with.
> would be nice to record the remote host/port



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