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
{{ message }}
This repository has been archived by the owner on Dec 16, 2024. It is now read-only.
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.
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: