From 1724fa5c1851216bfc2a1885cff061ba54d5a989 Mon Sep 17 00:00:00 2001 From: pabloFuente Date: Fri, 20 Feb 2026 14:10:57 +0100 Subject: [PATCH] Add use_global_cpu_monitoring and min_disk_space_mb to egress config --- community/egress.yaml | 12 ++++++++++-- pro/egress.yaml | 10 +++++++++- 2 files changed, 19 insertions(+), 3 deletions(-) diff --git a/community/egress.yaml b/community/egress.yaml index 2e72583..0890f7c 100644 --- a/community/egress.yaml +++ b/community/egress.yaml @@ -46,8 +46,16 @@ cpu_cost: openvidu: # Allocation strategy for new egress requests # - cpuload: the node with the lowest CPU load will be selected. Distributes the CPU load evenly across all nodes. - # - binpack: some node already hosting at least one Egress will be selected. Fills up nodes before assigning work to new ones. + # - binpack: some node already hosting at least one egress will be selected. Fills up nodes before assigning work to new ones. allocation_strategy: cpuload + # Whether to use system-wide CPU monitoring or egress process CPU monitoring. This affects the allocation of new egress requests. + # It is preferable to set this value to: + # - true: when the egress service is running in a shared server also hosting other CPU-intensive services. + # - false: when the egress service is running in a dedicated server. + use_global_cpu_monitoring: true # Disables the automatic killing of the most expensive egress when CPU is overloaded. # The default "false" value helps keeping the node stable, but may cause unexpected egress terminations under high load. - disable_cpu_overload_killer: false \ No newline at end of file + disable_cpu_overload_killer: false + # Minimum available disk space in MB required to accept new egress requests. + # Default: 512 MB. Set to a negative value (e.g., -1) to disable disk space checking. + min_disk_space_mb: 512 \ No newline at end of file diff --git a/pro/egress.yaml b/pro/egress.yaml index b81790b..6077ff1 100644 --- a/pro/egress.yaml +++ b/pro/egress.yaml @@ -46,8 +46,16 @@ cpu_cost: openvidu: # Allocation strategy for new egress requests # - cpuload: the node with the lowest CPU load will be selected. Distributes the CPU load evenly across all nodes. - # - binpack: some node already hosting at least one Egress will be selected. Fills up nodes before assigning work to new ones. + # - binpack: some node already hosting at least one egress will be selected. Fills up nodes before assigning work to new ones. allocation_strategy: cpuload + # Whether to use system-wide CPU monitoring or egress process CPU monitoring. This affects the allocation of new egress requests. + # It is preferable to set this value to: + # - true: when the egress service is running in a shared server also hosting other CPU-intensive services. + # - false: when the egress service is running in a dedicated server. + use_global_cpu_monitoring: true # Disables the automatic killing of the most expensive egress when CPU is overloaded. # The default "false" value helps keeping the node stable, but may cause unexpected egress terminations under high load. disable_cpu_overload_killer: false + # Minimum available disk space in MB required to accept new egress requests. + # Default: 512 MB. Set to a negative value (e.g., -1) to disable disk space checking. + min_disk_space_mb: 512