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
Each supporting thread (Senate election, period job scheduling, job processing, etc.) raises an exception, but the master sidekiq process continues to survive, not being able to process any work sitting in the queue(s).
We've run into issues with this in production, with our Kubernetes cluster not knowing that the sidekiq process has effectively died and needs to be restarted.
The text was updated successfully, but these errors were encountered:
Ruby version: 2.5.0
Sidekiq 5.0.5 / Pro 3.5.4 / Ent 1.6.1
If Redis happens to be unavailable at startup time of the
sidekiq
process, currently, something like this will happen:Each supporting thread (Senate election, period job scheduling, job processing, etc.) raises an exception, but the master
sidekiq
process continues to survive, not being able to process any work sitting in the queue(s).We've run into issues with this in production, with our Kubernetes cluster not knowing that the
sidekiq
process has effectively died and needs to be restarted.The text was updated successfully, but these errors were encountered: