I get this same behavior with Kafka 0.10.1.0 using PlainLoginModule and
simply making the password different from expected on the client. We also
get this behavior when creating our own Authorizer and always returning
false. I can tell a retry is happing because the brokers get called at
least ever
Hi,
I refer to the broker behaviour, for most part without SASL the brokers do
respond but as soon as you put SASL into the mix it does hang whenever
there is something that goes wrong, i.e the broker doesn't provide a
response on the socket and the client waits reading a response that it
never ge
Hi Gerrit,
I think it's important to distinguish broker and client behaviour. The
clients can hang because they keep retrying when they get certain errors.
When it comes to the broker, it should give you errors as a general rule.
If you are aware of certain scenarios where it should give an error
If you mean authorization with kafka (not with kerberos) then yes, seems
that kafka stops responding when it doesn't get exactly what it expects :/
no errors just timeouts.
On Thu, Jan 19, 2017 at 8:59 PM, Christian wrote:
> Thanks for the response Gerrit! It seems like authorization has the sa
Thanks for the response Gerrit! It seems like authorization has the same
behavior. Have you experienced that as well?
On Thu, Jan 19, 2017 at 11:48 AM, Gerrit Jansen van Vuuren <
gerrit...@gmail.com> wrote:
> Hi,
>
> I've added kerberos support for https://github.com/gerritjvv/kafka-fast
> and
>
Hi,
I've added kerberos support for https://github.com/gerritjvv/kafka-fast and
have seen that the kafka brokers do not send any response if the SASL
authentication is not correct or accepted, thus causing the client to hang
while waiting for a response from kafka.
Some things that might help to
