This repository has been archived by the owner on Jan 24, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 136
[BUG] Should support delaying response to failed client authentication #668
Labels
Comments
I also noticed that when we use kafka broker, the error retry interval it's about 400ms, in KoP the retry interval it's about 100ms. |
We may need implement the KIP-306 to resolve this problem (https://cwiki.apache.org/confluence/display/KAFKA/KIP-306%3A+Configuration+for+Delaying+Response+to+Failed+Client+Authentication). |
Demogorgon314
changed the title
[BUG] When KoP enable authentication, if kafka client not config with authentication, the broker error logs is too many.
[BUG] Should support delaying response to failed client authentication
Sep 6, 2021
BewareMyPower
pushed a commit
that referenced
this issue
Sep 7, 2021
Fix #668 ## Motivation Performing authentication is one of the most expensive operation performed in the network thread, so much so that it could end up saturating them, preventing from getting any useful work from being done. ## Modifications * Support delay close on authentication failed. * Change logs level.
BewareMyPower
pushed a commit
that referenced
this issue
Sep 8, 2021
Fix #668 ## Motivation Performing authentication is one of the most expensive operation performed in the network thread, so much so that it could end up saturating them, preventing from getting any useful work from being done. ## Modifications * Support delay close on authentication failed. * Change logs level.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
When KoP enable authentication, if kafka client not config with authentication, the broker error logs is too many. We don't need the authentication error stack trace.
In ShutdownableThread Shutting down,Shutdown completed should be debug level logs.
In KafkaRequestHandler when channel close, should be debug level log too.
Important : We need implement KIP-306 to prevent potential DoS.
Expected behavior
Just like kafka broker
The text was updated successfully, but these errors were encountered: