-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
post_soft_action_delay not actually used #106
Comments
Good catch, thanks. Seems like I will think about how to fix this later.
-- this line may be safety removed. This is not how it should work.
No, the problem should be solved differently. |
Thanks for confirming. I am going to patch my local copy for now but likely not in a way others will want to use it. For the specific use case I'm trying I just need it to not do anything for some time, after it's implemented one soft corrective action. I want to block further checking for a defined period - prevent it from reacting too often on a runaway process that's re-spawning. Server use case. If you can cover that as an option in a future release, that would be great. Good tool otherwise, thanks for making it. |
Do you have any problem with the current version?
Nohang does nothing after implementing soft corrective action, it waits until the victim dies. If the victim does not respond on soft corrective action, nohang sends SIGKILL (after |
In fact, after soft corrective action, if |
You are right, I didn't know about victim_cache_time. That's what I need actually, to not touch the same victim too often even if it's to blame. That might be the easiest solution for what I need, I was trying to do it with the post_soft_action_delay at first (delay doing anything again after an action). |
nohang sends SIGTERM to one process only once. The next signal is SIGKILL after
|
I cannot see that post_soft_action_delay is actually being used to sleep after a soft corrective action.
Reviewed the code and only place I can find is here:
nohang/src/nohang
Line 2710 in cf6b213
Might be indenting problem, maybe this was intended to be placed outside of the except block?
The text was updated successfully, but these errors were encountered: