You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
git clone https://github.com/kjellwinblad/brod_gssapi.git
cd brod_gssapi
git checkout origin/kjell/example_not_working -b kjell/example_not_working
cd example
./up
docker-compose up brod_client
The last command runs brod_client/src/example.erl. It will fail when running the line brod:produce_sync_offset(client1, Topic, Partition, <<"FistKey">>, <<"FirstValue">>) which is ok since the Kafka server's advertised.listeners configuration is badly configured. However, we only get the error reason:
{reached_max_retries,no_leader_connection}
Expected Result
A logging message is produced every time the producer's connection fails with as much information as possible (the address and port it tries to connect to and if possible the reason for the failure etc). In the above example the log entry should contain the following info:
{error,{{sasl_auth_error,{sasl_fail,<<"SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provid"...>>}},
The text was updated successfully, but these errors were encountered:
How to reproduce:
Install docker and docker-compose
Do the following
The last command runs
brod_client/src/example.erl
. It will fail when running the linebrod:produce_sync_offset(client1, Topic, Partition, <<"FistKey">>, <<"FirstValue">>)
which is ok since the Kafka server'sadvertised.listeners
configuration is badly configured. However, we only get the error reason:{reached_max_retries,no_leader_connection}
Expected Result
A logging message is produced every time the producer's connection fails with as much information as possible (the address and port it tries to connect to and if possible the reason for the failure etc). In the above example the log entry should contain the following info:
The text was updated successfully, but these errors were encountered: