You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/10/02 20:36:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16636086#comment-16636086 ] 

ASF GitHub Bot commented on KAFKA-7475:
---------------------------------------

radai-rosenblatt opened a new pull request #5729: KAFKA-7475 - capture remote address on connection authetication errors, and log it
URL: https://github.com/apache/kafka/pull/5729
 
 
   Signed-off-by: radai-rosenblatt <ra...@gmail.com>
   
   *More detailed description of your change,
   if necessary. The PR title and PR message become
   the squashed commit message, so use a separate
   comment to ping reviewers.*
   
   *Summary of testing strategy (including rationale)
   for the feature or bug fix. Unit and/or integration
   tests are expected for any behaviour change and
   system tests should be considered for larger changes.*
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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
>            Priority: Major
>
> 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)