Project

General

Profile

Actions

Bug #18915

closed

We don't know when generation hooks takes more time than expected, massively impacting generation time

Added by François ARMAND 3 months ago. Updated about 2 months ago.

Status:
Released
Priority:
N/A
Category:
Performance and scalability
Target version:
Severity:
User visibility:
Effort required:
Priority:
0
Tags:

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.


Subtasks 1 (0 open1 closed)

Bug #19032: Hook timeout info must specify to add command near the top in the templateReleasedVincent MEMBRÉActions
Actions #1

Updated by François ARMAND 3 months ago

  • Status changed from New to In progress
Actions #2

Updated by François ARMAND 3 months 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
Actions #3

Updated by François ARMAND 2 months ago

  • Status changed from Pending technical review to Pending release
Actions #5

Updated by Vincent MEMBRÉ about 2 months 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.

Actions

Also available in: Atom PDF