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
Describe the bug
The reaper manager registration is subject to race conditions, which means multiple reapers can potentially start at the same time causing extra load in redis. Bug found on version v7.1.30.
Expected behavior
There should be only one reaper manager, even when running multiple Sidekiq processes.
Current behavior
The bug can be easily replicated using the following snippet:
As you can see multiple managers were registered, but there should only be one.
On our deployment, we have frequent Sidekiq restarts, which exacerbates this problem, and we ended up running over 20+ reaper managers at the same time, what cripples Redis performance.
The text was updated successfully, but these errors were encountered:
leandrogoe
changed the title
Reaper manager subejct to race conditions
Reaper manager registration is subejct to race conditions
Aug 4, 2023
leandrogoe
changed the title
Reaper manager registration is subejct to race conditions
Reaper manager registration is subject to race conditions
Aug 22, 2023
I am hoping #820 will help with this. I don't think that more than one process can be registered. It was likely just that the logging happened despite the registration not going through.
Describe the bug
The reaper manager registration is subject to race conditions, which means multiple reapers can potentially start at the same time causing extra load in redis. Bug found on version v7.1.30.
Expected behavior
There should be only one reaper manager, even when running multiple Sidekiq processes.
Current behavior
The bug can be easily replicated using the following snippet:
As you can see multiple managers were registered, but there should only be one.
On our deployment, we have frequent Sidekiq restarts, which exacerbates this problem, and we ended up running over 20+ reaper managers at the same time, what cripples Redis performance.
The text was updated successfully, but these errors were encountered: