|
If you were logged in you would be able to see more operations.
|
|
|
| Labels: |
|
| User impact: |
High
|
This is the collective item for the subj, may result in a number of linked issues/sub-tasks. Story:
- There should be a forcedShutdown() API call or the like, exposed publicly (e.g. up to a JMX operation). It should actually do the right job, i.e. terminate no matter what within a timeframe.
- Graceful shutdown should let the in-flight queues to empty before proceeding
- There should be overloaded version of the graceful shutdown call accepting an additional timeout parameter
- On graceful shutdown timeout, call the forced shutdown method. This could be implemented, e.g. by wrapping a graceful shutdown into a Runnable with a watchdog, and forcing the shutdown on expiry.
|
|
Description
|
This is the collective item for the subj, may result in a number of linked issues/sub-tasks. Story:
- There should be a forcedShutdown() API call or the like, exposed publicly (e.g. up to a JMX operation). It should actually do the right job, i.e. terminate no matter what within a timeframe.
- Graceful shutdown should let the in-flight queues to empty before proceeding
- There should be overloaded version of the graceful shutdown call accepting an additional timeout parameter
- On graceful shutdown timeout, call the forced shutdown method. This could be implemented, e.g. by wrapping a graceful shutdown into a Runnable with a watchdog, and forcing the shutdown on expiry.
|
Show » |
|
Improvement
Open
Minor
Graceful/Forceful shutdown with timeouts