Skip to content

Conversation

MrJoy
Copy link

@MrJoy MrJoy commented Sep 30, 2025

No description provided.

AlexSc added 4 commits August 6, 2024 09:51
This can happen if the process is doing something CPU intensive which
starves Sidekiq's heartbeat thready out for more than 60 seconds.
Relying on the sidekiq apis means getting sidekiq to stop once the memory
limit is exceeded involves:
- Spinning up a new thread
- Make a redis call
- Waiting for the sidekiq heartbeat thread to run

When servers are under heavy resource load this is too much and can result in RSS
continuing to grow and jobs continuing to process. So, immediately quiet the worker
to stop processing ASAP while we let everything else settle out.
@BuonOmo
Copy link
Collaborator

BuonOmo commented Oct 1, 2025

Hi @MrJoy and thank you for the contribution. The repo is not really maintained anymore. However, I am one of the former maintainer and could ensure a fork is updated. If you'd like that, I still have a few requests concerning your PR:

  • could you squash your commits into one conventionnal commit with thourough description ?
  • can you elaborate on why changing from raising to warning ? My two cents is that workers would restart when failed, hence this logic is already handled at a higher level.
  • to answer the previous question and make sure your commit is impactful, can you code tests ?

@MrJoy
Copy link
Author

MrJoy commented Oct 1, 2025

@BuonOmo I'll consult with my teammate who authored the changes and see what we can come up with!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants