Actions
Bug #18915
closed
We don't know when generation hooks takes more time than expected, massively impacting generation time
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:
To do
Fix check:
Checked
Regression:
Description
We have some generation hooks that happen for all nodes one time, and other that happen for each node. We have a timeout for them, but which is rather hight (5 minutes for a warning, 1 hour for timeout).
This is because we can't know in advance what is a normal time for a hook. Perhaps we could add an header or something in the name to tell rudder what is the expected timeout for that hook.
Updated by François ARMAND almost 4 years ago
- Status changed from New to In progress
Updated by François ARMAND almost 4 years ago
- 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/3508
Updated by François ARMAND over 3 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|6f297ecf48f775de3375835d7cb8ff1267cdae2f.
Updated by François ARMAND over 3 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ over 3 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.10 and 6.2.3 which were released today.
Updated by Vincent MEMBRÉ almost 2 years ago
- Related to Bug #22339: Hook timeout may not have the good value added
Actions