Hooks need to run on an dedicated thread pool
Performance and scalability
If hooks run on scala "global" threadpool, they risk to be blocked by whatever is also on that threadpool, especially since its policy is not to run as always async.
Moreover, we need a seperate log for hooks, and a warning log on very long hooks (on a dedicated logger that can be shutdown by user if he wants).
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/2269
- Subject changed from Missing log on hooks for generation to Hooks need to run on an other threadpool than scala global
- Description updated (diff)
- Assignee changed from Nicolas CHARLES to François ARMAND
- Status changed from Pending technical review to Pending release
- Subject changed from Hooks need to run on an other threadpool than scala global to Hooks need to run on an dedicated thread pool
This bug has been fixed in Rudder 5.0.12 which was released today.
Also available in: Atom