Project

General

Profile

Bug #15095

Hooks need to run on an dedicated thread pool

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

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

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).


Subtasks

Bug #15098: Duration import breaks compilation of PolicyWriterService.scalaPending releaseFrançois ARMANDActions

Related issues

Related to Rudder - Architecture #15102: Port NuProcess and RunHooks to ZIOPending releaseActions

Associated revisions

Revision 03441124 (diff)
Added by François ARMAND 2 months ago

Fixes #15095: Hooks need to run on an other threadpool than scala global

History

#1

Updated by François ARMAND 2 months ago

  • Status changed from New to In progress
#2

Updated by François ARMAND 2 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/2269
#3

Updated by François ARMAND 2 months ago

  • Subject changed from Missing log on hooks for generation to Hooks need to run on an other threadpool than scala global
  • Description updated (diff)
#4

Updated by Rudder Quality Assistant 2 months ago

  • Assignee changed from Nicolas CHARLES to François ARMAND
#5

Updated by François ARMAND 2 months ago

  • Status changed from Pending technical review to Pending release
#6

Updated by François ARMAND 2 months ago

#10

Updated by Alexis MOUSSET about 2 months ago

  • Subject changed from Hooks need to run on an other threadpool than scala global to Hooks need to run on an dedicated thread pool
#11

Updated by Vincent MEMBRÉ about 2 months ago

This bug has been fixed in Rudder 5.0.12 which was released today.

Also available in: Atom PDF