-
Notifications
You must be signed in to change notification settings - Fork 483
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SASL/SCRAM timeouts with 5 sec. Add -m flag to documentation / readme. #317
Comments
I think the error is fine, since I listed all 3 brokers instead of one. |
Will improve error message. |
edenhill
added a commit
that referenced
this issue
May 11, 2021
ns-mkusper
pushed a commit
to ns-mkusper/kcat
that referenced
this issue
Sep 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using
-X security.protocol=SASL_SSL -X sasl.mechanism=SCRAM-SHA-512
To fix my use case I needed to add
-m 10
. This could be documented better. I read it from a commit message.Is this normal, that SASL SCRAM takes longer?
For querying metadata, I get the correct response, but I also get this error concatenated at the end:
I'm using AWS MSK default configs.
Is this error normal?
The text was updated successfully, but these errors were encountered: