showuon commented on PR #12559: URL: https://github.com/apache/kafka/pull/12559#issuecomment-1229984353
@dajac, thanks for the comment. Yes, I agree with you that this could result in flooding the logs in highly loaded system. But still, if the client got blocked due to exceeding max connection limit, it's bad that there's no log in broker side. Expose the info via metrics is a good suggestion. At quick look, I can't find we have any metrics recording this info. I'll check it again later, if no, I'm going to propose a KIP for it. But back to this PR, it is still not good when this issue happened, but broker keeps silent, even if we have metric's help. Maybe we can log with DEBUG level like @divijvaidya 's suggestion, and user can see this log when troubleshooting issues. WDYT? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org