search

whatyouhide / redix

Fast, pipelined, resilient Redis driver for Elixir. šŸ›
http://hexdocs.pm/redix
MIT License
1.1k stars 122 forks source link

Redix connection process is occasionally not alive #225

Closed pvthuyen closed 2 years ago

pvthuyen commented 2 years ago

I am using Redix version 1.1.5, and I start the connection by including Redix as a children to my application's Supervisor. However, in production envrionment, I occasionally observer that when I send the commands to the Redis connection, it sometimes exits with the error: (exit) no process: the process is not alive or there's no process currently associated with the given name, possibly because its application isn't started.

Did this issue happen to anyone before?

whatyouhide commented 2 years ago

Hey @pvthuyen, the issue can happen for a few reasons, but it generally points to the fact that the Redix connection process is not alive. Unless you see crashes from the Redix process directly, signaling a bug in Redix, then it's unlikely that the issue is Redix itself. What I suspect might be happening is that something else in your supervision tree is crashing, the strategy is not :one_for_one, and the supervisor is restarting Redix as well as a consequence. That could lead to calls to the Redix process while it's being restarted, which would lead to the error above.

That said, as I mentioned, unless you see crashes from Redix itself for now Iā€™m closing the issue as it doesn't look like it's something to do with Redix itself. If you have more info that point to an issue in Redix, please feel free to reopen this! šŸ’Ÿ

pvthuyen commented 2 years ago

Hey @whatyouhide, I can confirm that the strategy for my supervision tree is :one_for_one and other processes are unlikely to crash. Does the Redix process have any sort of quota or limit? If this is not an issue from Redix, do you have any suggestions on how to fix this issue? I'm putting the context trace here as well:

Sentry.CrashError: ** (exit) no process: the process is not alive or there's no process currently associated with the given name, possibly because its application isn't started
  File "lib/redix/connection.ex", line 80, in Redix.Connection.pipeline/3
  File "lib/redix.ex", line 520, in Redix.noreply_pipeline/3
  File "gen_server.erl", line 733, in :gen_server.try_terminate/3
  File "gen_server.erl", line 918, in :gen_server.terminate/10
  File "proc_lib.erl", line 236, in :proc_lib.wake_up/3
whatyouhide commented 2 years ago

Does the Redix process have any sort of quota or limit?

No.

If this is not an issue from Redix, do you have any suggestions on how to fix this issue?

Start another process that monitors your Redix process and logs the reason why the Redix process exited. The stacktrace you posted just says that Sentry, which was calling Redix, found that Redix was not alive.