Actions
Bug #15095
closed
Hooks need to run on an dedicated thread pool
Status:
Released
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
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).
Updated by 
Updated by 
Updated by 
Updated by
Actions