-
Notifications
You must be signed in to change notification settings - Fork 279
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
Spawned reconnect_loop process is not terminated when the client is terminated #124
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If an eredis client fails its first connection-attempt it will
spawn_link
a re-connection process.This re-connection process will run until it succeeds.
But, if the connection attempts continuously fails and the user stops the eredis client, the spawned process is not terminated.
You will have an unexpected process running that attempts to connect to a previously used Redis instance.
A probable reason for this can be that eredis_client is stopped with reason
normal
, and an exit signal with reasonnormal
is ignored by the re-connection process. See http://erlang.org/doc/reference_manual/processes.html#receiving-exit-signalsThe text was updated successfully, but these errors were encountered: