-
Type: New Feature
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 8.3
-
Fix Version/s: 8.10
-
Component/s: Renditions
-
Tags:
For a long-running, CPU-intensive, AutomationRenditionBuilder-based lazy rendition job is periodically consuming all CPUs on all nodes in a production cluster.
A "renditionBuilder" Work Category needs to be defined that would allow to control the number of concurrently-running RenditionBuilder works across the system.
These works currently run in the "default" queue along with most other works which is a problem.