Key: |
QB-3036
|
Type: |
Improvement
|
Status: |
Resolved
|
Resolution: |
Fixed
|
Priority: |
Critical
|
Assignee: |
Robin Shen
|
Reporter: |
AlSt
|
Votes: |
0
|
Watchers: |
0
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 25/Aug/17 12:05 PM
Updated: 23/Nov/17 09:50 AM
|
|
Component/s: |
None
|
Affects Version/s: |
7.0.19
|
Fix Version/s: |
7.0.28
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
As far as I see the force kill of a command is triggered 5 seconds after the graceful kill if the process is not already gone.
We have some integration tests which need more time than 5 seconds to really shutdown everything.
Correct me if I'm wrong.
If I'm right please make the wait time configurable. This would avoid hanging processes which are not really in the process tree.
Basically the thing is that we start webservers which start workers. These workers are not in the process tree. Only the monitoring process. And when the monitoring process is killed before the workers were shut down they remain active.
|
Description
|
As far as I see the force kill of a command is triggered 5 seconds after the graceful kill if the process is not already gone.
We have some integration tests which need more time than 5 seconds to really shutdown everything.
Correct me if I'm wrong.
If I'm right please make the wait time configurable. This would avoid hanging processes which are not really in the process tree.
Basically the thing is that we start webservers which start workers. These workers are not in the process tree. Only the monitoring process. And when the monitoring process is killed before the workers were shut down they remain active. |
Show » |
|
is there any plan of implementing this?
Or maybe I got the time between the killing wrongly analyzed. Then please correct me.
But this would really help in getting a clean state on the build node after a build took too long or was cancelled.