Skip to content
This repository has been archived by the owner on Dec 16, 2024. It is now read-only.

Spawned reconnect_loop process is not terminated when the client is terminated #124

Open
bjosv opened this issue Sep 22, 2020 · 0 comments · Fixed by Nordix/eredis#17
Open

Comments

@bjosv
Copy link

bjosv commented Sep 22, 2020

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 reason normal is ignored by the re-connection process. See http://erlang.org/doc/reference_manual/processes.html#receiving-exit-signals

bjosv added a commit to bjosv/eredis that referenced this issue Sep 22, 2020
bjosv added a commit to bjosv/eredis that referenced this issue Sep 22, 2020
bjosv added a commit to bjosv/eredis that referenced this issue Sep 22, 2020
bjosv added a commit to bjosv/eredis that referenced this issue Sep 23, 2020
bjosv added a commit to Nordix/eredis that referenced this issue Sep 24, 2020
@bjosv bjosv reopened this Sep 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant