This is an automated email from the ASF dual-hosted git repository.
wenjun pushed a commit to branch dev
in repository https://gitbox.apache.org/repos/asf/dolphinscheduler.git
The following commit(s) were added to refs/heads/dev by this push:
new 2721e873ad [Chore] Increase server-load-protection thresholds (#17041)
2721e873ad is described below
commit 2721e873ad62ff6e5f4ea11724351a784c00dea4
Author: xiangzihao <[email protected]>
AuthorDate: Thu Mar 6 09:39:56 2025 +0800
[Chore] Increase server-load-protection thresholds (#17041)
---
.../mysql_with_mysql_registry/dolphinscheduler_env.sh | 14 ++++++++------
.../dolphinscheduler_env.sh | 14 ++++++++------
.../dolphinscheduler_env.sh | 14 ++++++++------
.../dolphinscheduler_env.sh | 14 ++++++++------
docs/docs/en/architecture/configuration.md | 16 ++++++++--------
docs/docs/zh/architecture/configuration.md | 8 ++++----
.../src/main/resources/application.yaml | 8 ++++----
.../src/test/resources/application.yaml | 8 ++++----
.../src/main/resources/application.yaml | 16 ++++++++--------
.../src/main/resources/application.yaml | 8 ++++----
10 files changed, 64 insertions(+), 56 deletions(-)
diff --git
a/.github/workflows/cluster-test/mysql_with_mysql_registry/dolphinscheduler_env.sh
b/.github/workflows/cluster-test/mysql_with_mysql_registry/dolphinscheduler_env.sh
index 1380770920..0ec5cb8b67 100755
---
a/.github/workflows/cluster-test/mysql_with_mysql_registry/dolphinscheduler_env.sh
+++
b/.github/workflows/cluster-test/mysql_with_mysql_registry/dolphinscheduler_env.sh
@@ -46,12 +46,14 @@ export
DATAX_LAUNCHER=${DATAX_LAUNCHER:-/opt/soft/datax/bin/datax.py}
export
PATH=$HADOOP_HOME/bin:$SPARK_HOME/bin:$PYTHON_LAUNCHER:$JAVA_HOME/bin:$HIVE_HOME/bin:$FLINK_HOME/bin:$DATAX_LAUNCHER:$PATH
-export
MASTER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.7
-export
MASTER_SERVER_LOAD_PROTECTION_MAX_JVM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.7
-export
MASTER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_MEMORY_USAGE_PERCENTAGE_THRESHOLDS=0.7
-export
WORKER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.7
-export
WORKER_SERVER_LOAD_PROTECTION_MAX_JVM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.7
-export
WORKER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_MEMORY_USAGE_PERCENTAGE_THRESHOLDS=0.7
+export
MASTER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export
MASTER_SERVER_LOAD_PROTECTION_MAX_JVM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export
MASTER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_MEMORY_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export MASTER_SERVER_LOAD_PROTECTION_MAX_DISK_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export
WORKER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export
WORKER_SERVER_LOAD_PROTECTION_MAX_JVM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export
WORKER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_MEMORY_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export WORKER_SERVER_LOAD_PROTECTION_MAX_DISK_USAGE_PERCENTAGE_THRESHOLDS=0.9
# applicationId auto collection related configuration, the following
configurations are unnecessary if setting appId.collect=log
#export HADOOP_CLASSPATH=`hadoop
classpath`:${DOLPHINSCHEDULER_HOME}/tools/libs/*
diff --git
a/.github/workflows/cluster-test/mysql_with_zookeeper_registry/dolphinscheduler_env.sh
b/.github/workflows/cluster-test/mysql_with_zookeeper_registry/dolphinscheduler_env.sh
index e3c2891295..d769a3a02d 100755
---
a/.github/workflows/cluster-test/mysql_with_zookeeper_registry/dolphinscheduler_env.sh
+++
b/.github/workflows/cluster-test/mysql_with_zookeeper_registry/dolphinscheduler_env.sh
@@ -45,12 +45,14 @@ export
DATAX_LAUNCHER=${DATAX_LAUNCHER:-/opt/soft/datax/bin/datax.py}
export
PATH=$HADOOP_HOME/bin:$SPARK_HOME/bin:$PYTHON_LAUNCHER:$JAVA_HOME/bin:$HIVE_HOME/bin:$FLINK_HOME/bin:$DATAX_LAUNCHER:$PATH
-export
MASTER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.7
-export
MASTER_SERVER_LOAD_PROTECTION_MAX_JVM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.7
-export
MASTER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_MEMORY_USAGE_PERCENTAGE_THRESHOLDS=0.7
-export
WORKER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.7
-export
WORKER_SERVER_LOAD_PROTECTION_MAX_JVM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.7
-export
WORKER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_MEMORY_USAGE_PERCENTAGE_THRESHOLDS=0.7
+export
MASTER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export
MASTER_SERVER_LOAD_PROTECTION_MAX_JVM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export
MASTER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_MEMORY_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export MASTER_SERVER_LOAD_PROTECTION_MAX_DISK_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export
WORKER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export
WORKER_SERVER_LOAD_PROTECTION_MAX_JVM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export
WORKER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_MEMORY_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export WORKER_SERVER_LOAD_PROTECTION_MAX_DISK_USAGE_PERCENTAGE_THRESHOLDS=0.9
# applicationId auto collection related configuration, the following
configurations are unnecessary if setting appId.collect=log
#export HADOOP_CLASSPATH=`hadoop
classpath`:${DOLPHINSCHEDULER_HOME}/tools/libs/*
diff --git
a/.github/workflows/cluster-test/postgresql_with_postgresql_registry/dolphinscheduler_env.sh
b/.github/workflows/cluster-test/postgresql_with_postgresql_registry/dolphinscheduler_env.sh
index ea2447c224..79a13d1a6a 100644
---
a/.github/workflows/cluster-test/postgresql_with_postgresql_registry/dolphinscheduler_env.sh
+++
b/.github/workflows/cluster-test/postgresql_with_postgresql_registry/dolphinscheduler_env.sh
@@ -46,12 +46,14 @@ export
DATAX_LAUNCHER=${DATAX_LAUNCHER:-/opt/soft/datax/bin/datax.py}
export
PATH=$HADOOP_HOME/bin:$SPARK_HOME/bin:$PYTHON_LAUNCHER:$JAVA_HOME/bin:$HIVE_HOME/bin:$FLINK_HOME/bin:$DATAX_LAUNCHER:$PATH
-export
MASTER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.7
-export
MASTER_SERVER_LOAD_PROTECTION_MAX_JVM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.7
-export
MASTER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_MEMORY_USAGE_PERCENTAGE_THRESHOLDS=0.7
-export
WORKER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.7
-export
WORKER_SERVER_LOAD_PROTECTION_MAX_JVM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.7
-export
WORKER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_MEMORY_USAGE_PERCENTAGE_THRESHOLDS=0.7
+export
MASTER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export
MASTER_SERVER_LOAD_PROTECTION_MAX_JVM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export
MASTER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_MEMORY_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export MASTER_SERVER_LOAD_PROTECTION_MAX_DISK_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export
WORKER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export
WORKER_SERVER_LOAD_PROTECTION_MAX_JVM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export
WORKER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_MEMORY_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export WORKER_SERVER_LOAD_PROTECTION_MAX_DISK_USAGE_PERCENTAGE_THRESHOLDS=0.9
# applicationId auto collection related configuration, the following
configurations are unnecessary if setting appId.collect=log
#export HADOOP_CLASSPATH=`hadoop
classpath`:${DOLPHINSCHEDULER_HOME}/tools/libs/*
diff --git
a/.github/workflows/cluster-test/postgresql_with_zookeeper_registry/dolphinscheduler_env.sh
b/.github/workflows/cluster-test/postgresql_with_zookeeper_registry/dolphinscheduler_env.sh
index 021f1319d2..05f3203b50 100644
---
a/.github/workflows/cluster-test/postgresql_with_zookeeper_registry/dolphinscheduler_env.sh
+++
b/.github/workflows/cluster-test/postgresql_with_zookeeper_registry/dolphinscheduler_env.sh
@@ -45,12 +45,14 @@ export
DATAX_LAUNCHER=${DATAX_LAUNCHER:-/opt/soft/datax/bin/datax.py}
export
PATH=$HADOOP_HOME/bin:$SPARK_HOME/bin:$PYTHON_LAUNCHER:$JAVA_HOME/bin:$HIVE_HOME/bin:$FLINK_HOME/bin:$DATAX_LAUNCHER:$PATH
-export
MASTER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.7
-export
MASTER_SERVER_LOAD_PROTECTION_MAX_JVM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.7
-export
MASTER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_MEMORY_USAGE_PERCENTAGE_THRESHOLDS=0.7
-export
WORKER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.7
-export
WORKER_SERVER_LOAD_PROTECTION_MAX_JVM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.7
-export
WORKER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_MEMORY_USAGE_PERCENTAGE_THRESHOLDS=0.7
+export
MASTER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export
MASTER_SERVER_LOAD_PROTECTION_MAX_JVM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export
MASTER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_MEMORY_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export MASTER_SERVER_LOAD_PROTECTION_MAX_DISK_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export
WORKER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export
WORKER_SERVER_LOAD_PROTECTION_MAX_JVM_CPU_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export
WORKER_SERVER_LOAD_PROTECTION_MAX_SYSTEM_MEMORY_USAGE_PERCENTAGE_THRESHOLDS=0.9
+export WORKER_SERVER_LOAD_PROTECTION_MAX_DISK_USAGE_PERCENTAGE_THRESHOLDS=0.9
# applicationId auto collection related configuration, the following
configurations are unnecessary if setting appId.collect=log
#export HADOOP_CLASSPATH=`hadoop
classpath`:${DOLPHINSCHEDULER_HOME}/tools/libs/*
diff --git a/docs/docs/en/architecture/configuration.md
b/docs/docs/en/architecture/configuration.md
index 742e6b8be0..10f8184185 100644
--- a/docs/docs/en/architecture/configuration.md
+++ b/docs/docs/en/architecture/configuration.md
@@ -282,10 +282,10 @@ Location: `master-server/conf/application.yaml`
| master.worker-load-balancer-configuration-properties.type
| DYNAMIC_WEIGHTED_ROUND_ROBIN | Master will use the worker's
cpu/memory/threadPool usage to calculate the worker load, the lower load will
have more change to be dispatched task |
| master.max-heartbeat-interval
| 10s | master max heartbeat interval
|
| master.server-load-protection.enabled
| true | If set true, will open master overload
protection
|
-| master.server-load-protection.max-system-cpu-usage-percentage-thresholds
| 0.7 | Master max system cpu usage, when the master's
system cpu usage is smaller then this value, master server can execute
workflow. |
-| master.server-load-protection.max-jvm-cpu-usage-percentage-thresholds
| 0.7 | Master max JVM cpu usage, when the master's
jvm cpu usage is smaller then this value, master server can execute workflow.
|
-| master.server-load-protection.max-system-memory-usage-percentage-thresholds
| 0.7 | Master max system memory usage , when the
master's system memory usage is smaller then this value, master server can
execute workflow. |
-| master.server-load-protection.max-disk-usage-percentage-thresholds
| 0.7 | Master max disk usage , when the master's disk
usage is smaller then this value, master server can execute workflow.
|
+| master.server-load-protection.max-system-cpu-usage-percentage-thresholds
| 0.8 | Master max system cpu usage, when the master's
system cpu usage is smaller then this value, master server can execute
workflow. |
+| master.server-load-protection.max-jvm-cpu-usage-percentage-thresholds
| 0.8 | Master max JVM cpu usage, when the master's
jvm cpu usage is smaller then this value, master server can execute workflow.
|
+| master.server-load-protection.max-system-memory-usage-percentage-thresholds
| 0.8 | Master max system memory usage , when the
master's system memory usage is smaller then this value, master server can
execute workflow. |
+| master.server-load-protection.max-disk-usage-percentage-thresholds
| 0.8 | Master max disk usage , when the master's disk
usage is smaller then this value, master server can execute workflow.
|
| master.worker-group-refresh-interval
| 10s | The interval to refresh worker group from db
to memory
|
| master.command-fetch-strategy.type
| ID_SLOT_BASED | The command fetch strategy, only support
`ID_SLOT_BASED`
|
| master.command-fetch-strategy.config.id-step
| 1 | The id auto incremental step of t_ds_command
in db
|
@@ -301,10 +301,10 @@ Location: `worker-server/conf/application.yaml`
| worker.max-heartbeat-interval
| 10s | worker-service max heartbeat interval
|
| worker.host-weight
| 100 | worker host weight to dispatch tasks
|
| worker.server-load-protection.enabled
| true | If set true will open worker overload protection
|
-| worker.server-load-protection.max-system-cpu-usage-percentage-thresholds
| 0.7 | Worker max system cpu usage, when the worker's system cpu
usage is smaller then this value, master server can execute workflow.
|
-| worker.server-load-protection.max-jvm-cpu-usage-percentage-thresholds
| 0.7 | Worker max JVM cpu usage, when the worker's jvm cpu usage is
smaller then this value, master server can execute workflow.
|
-| worker.server-load-protection.max-system-memory-usage-percentage-thresholds
| 0.7 | Worker max system memory usage , when the worker's system
memory usage is smaller then this value, master server can execute workflow.
|
-| worker.server-load-protection.max-disk-usage-percentage-thresholds
| 0.7 | Worker max disk usage , when the worker's disk usage is
smaller then this value, master server can execute workflow.
|
+| worker.server-load-protection.max-system-cpu-usage-percentage-thresholds
| 0.8 | Worker max system cpu usage, when the worker's system cpu
usage is smaller then this value, master server can execute workflow.
|
+| worker.server-load-protection.max-jvm-cpu-usage-percentage-thresholds
| 0.8 | Worker max JVM cpu usage, when the worker's jvm cpu usage is
smaller then this value, master server can execute workflow.
|
+| worker.server-load-protection.max-system-memory-usage-percentage-thresholds
| 0.8 | Worker max system memory usage , when the worker's system
memory usage is smaller then this value, master server can execute workflow.
|
+| worker.server-load-protection.max-disk-usage-percentage-thresholds
| 0.8 | Worker max disk usage , when the worker's disk usage is
smaller then this value, master server can execute workflow.
|
| worker.registry-disconnect-strategy.strategy
| stop | Used when the worker disconnect from registry, default value:
stop. Optional values include stop, waiting
|
| worker.registry-disconnect-strategy.max-waiting-time
| 100s | Used when the worker disconnect from registry, and the
disconnect strategy is waiting, this config means the worker will waiting to
reconnect to registry in given times, and after the waiting times, if the
worker still cannot connect to registry, will stop itself, if the value is 0s,
will wait infinitely |
| worker.physical-task-config.task-executor-thread-size
| 100 | The thread size used to execute physical task
|
diff --git a/docs/docs/zh/architecture/configuration.md
b/docs/docs/zh/architecture/configuration.md
index 83c076c7c5..e19b1470b2 100644
--- a/docs/docs/zh/architecture/configuration.md
+++ b/docs/docs/zh/architecture/configuration.md
@@ -309,10 +309,10 @@ common.properties配置文件目前主要是配置hadoop/s3/yarn/applicationId
| worker.host-weight
| 100 | 派发任务时，worker主机的权重
|
| worker.tenant-auto-create
| true |
租户对应于系统的用户,由worker提交作业.如果系统没有该用户,则在参数worker.tenant.auto.create为true后自动创建。
|
| worker.server-load-protection.enabled
| true | 是否开启系统保护策略
|
-| worker.server-load-protection.max-system-cpu-usage-percentage-thresholds
| 0.7 | worker最大系统cpu使用值,只有当前系统cpu使用值低于最大系统cpu使用值,worker服务才能接收任务.
默认值为0.7: 会使用70%的操作系统CPU |
-| worker.server-load-protection.max-jvm-cpu-usage-percentage-thresholds
| 0.7 | worker最大JVM cpu使用值,只有当前JVM cpu使用值低于最大JVM cpu使用值,worker服务才能接收任务.
默认值为0.7: 会使用70%的JVM CPU |
-| worker.server-load-protection.max-system-memory-usage-percentage-thresholds
| 0.7 | worker最大系统 内存使用值,只有当前系统内存使用值低于最大系统内存使用值,worker服务才能接收任务. 默认值为0.7:
会使用70%的操作系统内存 |
-| worker.server-load-protection.max-disk-usage-percentage-thresholds
| 0.7 | worker最大系统磁盘使用值,只有当前系统磁盘使用值低于最大系统磁盘使用值,worker服务才能接收任务. 默认值为0.7:
会使用70%的操作系统磁盘空间 |
+| worker.server-load-protection.max-system-cpu-usage-percentage-thresholds
| 0.8 | worker最大系统cpu使用值,只有当前系统cpu使用值低于最大系统cpu使用值,worker服务才能接收任务.
默认值为0.8: 会使用80%的操作系统CPU |
+| worker.server-load-protection.max-jvm-cpu-usage-percentage-thresholds
| 0.8 | worker最大JVM cpu使用值,只有当前JVM cpu使用值低于最大JVM cpu使用值,worker服务才能接收任务.
默认值为0.8: 会使用80%的JVM CPU |
+| worker.server-load-protection.max-system-memory-usage-percentage-thresholds
| 0.8 | worker最大系统 内存使用值,只有当前系统内存使用值低于最大系统内存使用值,worker服务才能接收任务. 默认值为0.8:
会使用80%的操作系统内存 |
+| worker.server-load-protection.max-disk-usage-percentage-thresholds
| 0.8 | worker最大系统磁盘使用值,只有当前系统磁盘使用值低于最大系统磁盘使用值,worker服务才能接收任务. 默认值为0.8:
会使用80%的操作系统磁盘空间 |
| worker.alert-listen-host
| localhost | alert监听host
|
| worker.alert-listen-port
| 50052 | alert监听端口
|
| worker.physical-task-config.task-executor-thread-size
| 100 | Worker中任务最大并发度
|
diff --git a/dolphinscheduler-master/src/main/resources/application.yaml
b/dolphinscheduler-master/src/main/resources/application.yaml
index bb402a1ed8..e003a9ee09 100644
--- a/dolphinscheduler-master/src/main/resources/application.yaml
+++ b/dolphinscheduler-master/src/main/resources/application.yaml
@@ -94,13 +94,13 @@ master:
# If set true, will open master overload protection
enabled: true
# Master max system cpu usage, when the master's system cpu usage is
smaller then this value, master server can execute workflow.
- max-system-cpu-usage-percentage-thresholds: 0.7
+ max-system-cpu-usage-percentage-thresholds: 0.8
# Master max jvm cpu usage, when the master's jvm cpu usage is smaller
then this value, master server can execute workflow.
- max-jvm-cpu-usage-percentage-thresholds: 0.7
+ max-jvm-cpu-usage-percentage-thresholds: 0.8
# Master max System memory usage , when the master's system memory usage
is smaller then this value, master server can execute workflow.
- max-system-memory-usage-percentage-thresholds: 0.7
+ max-system-memory-usage-percentage-thresholds: 0.8
# Master max disk usage , when the master's disk usage is smaller then
this value, master server can execute workflow.
- max-disk-usage-percentage-thresholds: 0.7
+ max-disk-usage-percentage-thresholds: 0.8
worker-group-refresh-interval: 5m
command-fetch-strategy:
type: ID_SLOT_BASED
diff --git a/dolphinscheduler-master/src/test/resources/application.yaml
b/dolphinscheduler-master/src/test/resources/application.yaml
index 8fdf521cde..ddbe80cf4c 100644
--- a/dolphinscheduler-master/src/test/resources/application.yaml
+++ b/dolphinscheduler-master/src/test/resources/application.yaml
@@ -57,13 +57,13 @@ master:
# If set true, will open master overload protection
enabled: true
# Master max system cpu usage, when the master's system cpu usage is
smaller then this value, master server can execute workflow.
- max-system-cpu-usage-percentage-thresholds: 0.90
+ max-system-cpu-usage-percentage-thresholds: 0.9
# Master max jvm cpu usage, when the master's jvm cpu usage is smaller
then this value, master server can execute workflow.
- max-jvm-cpu-usage-percentage-thresholds: 0.90
+ max-jvm-cpu-usage-percentage-thresholds: 0.9
# Master max System memory usage , when the master's system memory usage
is smaller then this value, master server can execute workflow.
- max-system-memory-usage-percentage-thresholds: 0.90
+ max-system-memory-usage-percentage-thresholds: 0.9
# Master max disk usage , when the master's disk usage is smaller then
this value, master server can execute workflow.
- max-disk-usage-percentage-thresholds: 0.90
+ max-disk-usage-percentage-thresholds: 0.9
worker-load-balancer-configuration-properties:
# RANDOM, ROUND_ROBIN, FIXED_WEIGHTED_ROUND_ROBIN,
DYNAMIC_WEIGHTED_ROUND_ROBIN
type: DYNAMIC_WEIGHTED_ROUND_ROBIN
diff --git
a/dolphinscheduler-standalone-server/src/main/resources/application.yaml
b/dolphinscheduler-standalone-server/src/main/resources/application.yaml
index 4f78b91c04..577bed72da 100644
--- a/dolphinscheduler-standalone-server/src/main/resources/application.yaml
+++ b/dolphinscheduler-standalone-server/src/main/resources/application.yaml
@@ -163,13 +163,13 @@ master:
server-load-protection:
enabled: true
# Master max system cpu usage, when the master's system cpu usage is
smaller then this value, master server can execute workflow.
- max-system-cpu-usage-percentage-thresholds: 1
+ max-system-cpu-usage-percentage-thresholds: 0.8
# Master max jvm cpu usage, when the master's jvm cpu usage is smaller
then this value, master server can execute workflow.
- max-jvm-cpu-usage-percentage-thresholds: 0.9
+ max-jvm-cpu-usage-percentage-thresholds: 0.8
# Master max System memory usage , when the master's system memory usage
is smaller then this value, master server can execute workflow.
- max-system-memory-usage-percentage-thresholds: 0.9
+ max-system-memory-usage-percentage-thresholds: 0.8
# Master max disk usage , when the master's disk usage is smaller then
this value, master server can execute workflow.
- max-disk-usage-percentage-thresholds: 0.9
+ max-disk-usage-percentage-thresholds: 0.8
worker-load-balancer-configuration-properties:
# RANDOM, ROUND_ROBIN, FIXED_WEIGHTED_ROUND_ROBIN,
DYNAMIC_WEIGHTED_ROUND_ROBIN
type: DYNAMIC_WEIGHTED_ROUND_ROBIN
@@ -199,13 +199,13 @@ worker:
server-load-protection:
enabled: true
# Worker max system cpu usage, when the worker's system cpu usage is
smaller then this value, worker server can be dispatched tasks.
- max-system-cpu-usage-percentage-thresholds: 1
+ max-system-cpu-usage-percentage-thresholds: 0.8
# Worker max jvm cpu usage, when the worker's jvm cpu usage is smaller
then this value, worker server can be dispatched tasks.
- max-jvm-cpu-usage-percentage-thresholds: 0.9
+ max-jvm-cpu-usage-percentage-thresholds: 0.8
# Worker max System memory usage , when the worker's system memory usage
is smaller then this value, worker server can be dispatched tasks.
- max-system-memory-usage-percentage-thresholds: 0.9
+ max-system-memory-usage-percentage-thresholds: 0.8
# Worker max disk usage , when the worker's disk usage is smaller then
this value, worker server can be dispatched tasks.
- max-disk-usage-percentage-thresholds: 0.9
+ max-disk-usage-percentage-thresholds: 0.8
physical-task-config:
# The number of threads in the Physical task engine that used to execute
tasks
task-executor-thread-size: 100
diff --git a/dolphinscheduler-worker/src/main/resources/application.yaml
b/dolphinscheduler-worker/src/main/resources/application.yaml
index f463eff337..cb3b9c514f 100644
--- a/dolphinscheduler-worker/src/main/resources/application.yaml
+++ b/dolphinscheduler-worker/src/main/resources/application.yaml
@@ -52,13 +52,13 @@ worker:
# If set true, will open worker overload protection
enabled: true
# Worker max system cpu usage, when the worker's system cpu usage is
smaller then this value, worker server can be dispatched tasks.
- max-system-cpu-usage-percentage-thresholds: 0.7
+ max-system-cpu-usage-percentage-thresholds: 0.8
# Worker max jvm cpu usage, when the worker's jvm cpu usage is smaller
then this value, worker server can be dispatched tasks.
- max-jvm-cpu-usage-percentage-thresholds: 0.7
+ max-jvm-cpu-usage-percentage-thresholds: 0.8
# Worker max System memory usage , when the master's system memory usage
is smaller then this value, master server can execute workflow.
- max-system-memory-usage-percentage-thresholds: 0.7
+ max-system-memory-usage-percentage-thresholds: 0.8
# Worker max disk usage , when the worker's disk usage is smaller then
this value, worker server can be dispatched tasks.
- max-disk-usage-percentage-thresholds: 0.7
+ max-disk-usage-percentage-thresholds: 0.8
task-execute-threads-full-policy: REJECT
physical-task-config:
# The number of threads in the Physical task engine that used to execute
tasks
