This is an automated email from the ASF dual-hosted git repository.
yiguolei pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git
The following commit(s) were added to refs/heads/master by this push:
new 4e508c4e1a2 remove enable_query_memory_overcommit related docs since
it is not supported any more (#3419)
4e508c4e1a2 is described below
commit 4e508c4e1a2cc00117ebc69f4c5d9a06f6f87dfc
Author: yiguolei <[email protected]>
AuthorDate: Fri Feb 27 16:10:38 2026 +0800
remove enable_query_memory_overcommit related docs since it is not
supported any more (#3419)
## Versions
- [x] dev
- [x] 4.x
- [ ] 3.x
- [ ] 2.1
## Languages
- [ ] Chinese
- [ ] English
## Docs Checklist
- [ ] Checked by AI
- [ ] Test Cases Built
Co-authored-by: yiguolei <[email protected]>
---
docs/admin-manual/config/be-config.md | 5 -----
.../memory-management/memory-analysis/oom-crash-analysis.md | 2 +-
.../memory-analysis/query-cancelled-after-query-memory-exceeded.md | 3 ---
.../current/admin-manual/config/be-config.md | 5 -----
.../memory-management/memory-analysis/oom-crash-analysis.md | 2 +-
.../memory-analysis/query-cancelled-after-query-memory-exceeded.md | 2 --
.../version-4.x/admin-manual/config/be-config.md | 5 -----
.../memory-management/memory-analysis/oom-crash-analysis.md | 2 +-
.../memory-analysis/query-cancelled-after-query-memory-exceeded.md | 2 --
versioned_docs/version-2.1/admin-manual/config/be-config.md | 1 -
versioned_docs/version-4.x/admin-manual/config/be-config.md | 5 -----
.../memory-management/memory-analysis/oom-crash-analysis.md | 2 +-
.../memory-analysis/query-cancelled-after-query-memory-exceeded.md | 2 --
13 files changed, 4 insertions(+), 34 deletions(-)
diff --git a/docs/admin-manual/config/be-config.md
b/docs/admin-manual/config/be-config.md
index d229eccf7d9..d306ba7eb60 100644
--- a/docs/admin-manual/config/be-config.md
+++ b/docs/admin-manual/config/be-config.md
@@ -1320,11 +1320,6 @@ Indicates how many tablets failed to load in the data
directory. At the same tim
* Description: Whether enable simdjson to parse json while stream load
* Default value: true
-#### `enable_query_memory_overcommit`
-
-* Description: If true, when the process does not exceed the soft mem limit,
the query memory will not be limited; when the process memory exceeds the soft
mem limit, the query with the largest ratio between the currently used memory
and the exec_mem_limit will be canceled. If false, cancel query when the memory
used exceeds `exec_mem_limit`.
-* Default value: true
-
#### `user_files_secure_path`
* Description: The storage directory for files queried by `local` table valued
functions.
diff --git
a/docs/admin-manual/trouble-shooting/memory-management/memory-analysis/oom-crash-analysis.md
b/docs/admin-manual/trouble-shooting/memory-management/memory-analysis/oom-crash-analysis.md
index 1ba24d5aa25..1e9a0e8edc3 100644
---
a/docs/admin-manual/trouble-shooting/memory-management/memory-analysis/oom-crash-analysis.md
+++
b/docs/admin-manual/trouble-shooting/memory-management/memory-analysis/oom-crash-analysis.md
@@ -36,7 +36,7 @@ If the following phenomenon is met, it can be considered that
the cluster memory
At this time, refer to [BE Configuration Items](../../../config/be-config) to
reduce `mem_limit` and increase `max_sys_mem_available_low_water_mark_bytes` in
`be/conf/be.conf`. For more information about memory limits, watermark
calculation methods, and memory GC, see [Memory Control
Strategy](./../memory-feature/memory-control-strategy.md).
-In addition, other parameters can be adjusted to control memory status refresh
and GC, including `memory_gc_sleep_time_ms`, `soft_mem_limit_frac`,
`memory_maintenance_sleep_time_ms`, `process_minor_gc_size`,
`process_full_gc_size`, `enable_query_memory_overcommit`,
`thread_wait_gc_max_milliseconds`, etc.
+In addition, other parameters can be adjusted to control memory status refresh
and GC, including `memory_gc_sleep_time_ms`, `soft_mem_limit_frac`,
`memory_maintenance_sleep_time_ms`, `process_minor_gc_size`,
`process_full_gc_size`, `thread_wait_gc_max_milliseconds`, etc.
## Some abnormal problems trigger OOM Killer
diff --git
a/docs/admin-manual/trouble-shooting/memory-management/memory-analysis/query-cancelled-after-query-memory-exceeded.md
b/docs/admin-manual/trouble-shooting/memory-management/memory-analysis/query-cancelled-after-query-memory-exceeded.md
index c2cdf347c5b..454cee39944 100644
---
a/docs/admin-manual/trouble-shooting/memory-management/memory-analysis/query-cancelled-after-query-memory-exceeded.md
+++
b/docs/admin-manual/trouble-shooting/memory-management/memory-analysis/query-cancelled-after-query-memory-exceeded.md
@@ -23,9 +23,6 @@ The error message is divided into two parts:
## Single execution memory limit and memory over-issuance
`show variables;` You can view Doris Session Veriable, where `exec_mem_limit`
is the execution memory limit for a single query and load, but since Doris 1.2,
query memory over-issuance (overcommit) is supported, aiming to allow queries
to set more flexible memory limits. When there is sufficient memory, even if
the query memory exceeds the upper limit, it will not be Cancel, so users
usually do not need to pay attention to query memory usage. Until the memory is
insufficient, the query w [...]
-
-If you want to turn off query memory over-issuance, refer to [BE Configuration
Items](../../../config/be-config) and add
`enable_query_memory_overcommit=false` in `conf/be.conf`. At this time, a
single query and load memory exceeding `exec_mem_limit` will be canceled. If
you want to avoid the negative impact of large queries on cluster stability, or
want to accurately control the execution of tasks on the cluster to ensure
sufficient stability, then you can consider turning off query mem [...]
-
## Query Memory Analysis
If you need to analyze the memory usage of queries, refer to [Query Memory
Analysis](./query-memory-analysis.md).
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/config/be-config.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/config/be-config.md
index 2fde3f7fa70..c0ea7d7baa3 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/config/be-config.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/config/be-config.md
@@ -1291,11 +1291,6 @@ load tablets from header failed, failed tablets size:
xxx, path=xxx
* 描述：是否在导入 json 数据时用 simdjson 来解析。
* 默认值：true
-#### `enable_query_memory_overcommit`
-
-* 描述：如果为 true，则当内存未超过 exec_mem_limit 时，查询内存将不受限制；当进程内存超过 exec_mem_limit 且大于
2GB 时，查询会被取消。如果为 false，则在使用的内存超过 exec_mem_limit 时取消查询。
-* 默认值：true
-
#### `user_files_secure_path`
* 描述：`local` 表函数查询的文件的存储目录。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/trouble-shooting/memory-management/memory-analysis/oom-crash-analysis.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/trouble-shooting/memory-management/memory-analysis/oom-crash-analysis.md
index 1385c047197..02e435c38f9 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/trouble-shooting/memory-management/memory-analysis/oom-crash-analysis.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/trouble-shooting/memory-management/memory-analysis/oom-crash-analysis.md
@@ -36,7 +36,7 @@
此时参考 [BE 配置项](../../../config/be-config) 在`be/conf/be.conf`中调小`mem_limit`，调大
`max_sys_mem_available_low_water_mark_bytes`，有关内存限制和水位线计算方法、内存 GC 的更多介绍见
[内存控制策略](./../memory-feature/memory-control-strategy.md)。
-此外还可以调节其他参数控制内存状态刷新和 GC，包括
`memory_gc_sleep_time_ms`，`soft_mem_limit_frac`，`memory_maintenance_sleep_time_ms`，`process_minor_gc_size`，`process_full_gc_size`，`enable_query_memory_overcommit`，`thread_wait_gc_max_milliseconds`
等。
+此外还可以调节其他参数控制内存状态刷新和 GC，包括
`memory_gc_sleep_time_ms`，`soft_mem_limit_frac`，`memory_maintenance_sleep_time_ms`，`process_minor_gc_size`，`process_full_gc_size`，`thread_wait_gc_max_milliseconds`
等。
## 一些异常问题导致触发 OOM Killer
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/trouble-shooting/memory-management/memory-analysis/query-cancelled-after-query-memory-exceeded.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/trouble-shooting/memory-management/memory-analysis/query-cancelled-after-query-memory-exceeded.md
index 82b43a88572..262031de794 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/trouble-shooting/memory-management/memory-analysis/query-cancelled-after-query-memory-exceeded.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/trouble-shooting/memory-management/memory-analysis/query-cancelled-after-query-memory-exceeded.md
@@ -24,8 +24,6 @@ ERROR 1105 (HY000): errCode = 2, detailMessage =
(10.16.10.8)[MEM_LIMIT_EXCEEDED
`show variables;` 可以查看 Doris Session Veriable，其中的 `exec_mem_limit`
是单次查询和导入的执行内存限制，但从 Doris 1.2 开始支持查询内存超发
(overcommit)，旨在允许查询设置更灵活的内存限制，内存充足时即使查询内存超过上限也不会被
Cancel，所以通常用户无需关注查询内存使用。直到内存不足时，查询会在尝试分配新内存时等待一段时间，此时会基于一定规则优先 Cancel
`mem_used` 与 `exec_mem_limit` 比值大的
Query。如果等待过程中内存释放的大小满足需求，查询将继续执行，否则将抛出异常并终止查询。
-如果希望关闭查询内存超发，参考 [BE 配置项](../../../config/be-config)，在 `conf/be.conf` 中增加
`enable_query_memory_overcommit=false`，此时单次查询和导入的内存超过 `exec_mem_limit` 即会被
Cancel。如果你希望避免大查询对集群稳定性造成的负面影响，或者希望准确控制集群上的任务执行来保证足够的稳定性，那么可以考虑关闭查询内存超发。
-
## 查询内存分析
如果需要分析查询的内存使用，参考 [查询内存分析](./query-memory-analysis.md)。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/config/be-config.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/config/be-config.md
index 1ceca55ec4d..fe596c378b2 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/config/be-config.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/config/be-config.md
@@ -1279,11 +1279,6 @@ load tablets from header failed, failed tablets size:
xxx, path=xxx
* 描述：是否在导入 json 数据时用 simdjson 来解析。
* 默认值：true
-#### `enable_query_memory_overcommit`
-
-* 描述：如果为 true，则当内存未超过 exec_mem_limit 时，查询内存将不受限制；当进程内存超过 exec_mem_limit 且大于
2GB 时，查询会被取消。如果为 false，则在使用的内存超过 exec_mem_limit 时取消查询。
-* 默认值：true
-
#### `user_files_secure_path`
* 描述：`local` 表函数查询的文件的存储目录。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/trouble-shooting/memory-management/memory-analysis/oom-crash-analysis.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/trouble-shooting/memory-management/memory-analysis/oom-crash-analysis.md
index 1385c047197..02e435c38f9 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/trouble-shooting/memory-management/memory-analysis/oom-crash-analysis.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/trouble-shooting/memory-management/memory-analysis/oom-crash-analysis.md
@@ -36,7 +36,7 @@
此时参考 [BE 配置项](../../../config/be-config) 在`be/conf/be.conf`中调小`mem_limit`，调大
`max_sys_mem_available_low_water_mark_bytes`，有关内存限制和水位线计算方法、内存 GC 的更多介绍见
[内存控制策略](./../memory-feature/memory-control-strategy.md)。
-此外还可以调节其他参数控制内存状态刷新和 GC，包括
`memory_gc_sleep_time_ms`，`soft_mem_limit_frac`，`memory_maintenance_sleep_time_ms`，`process_minor_gc_size`，`process_full_gc_size`，`enable_query_memory_overcommit`，`thread_wait_gc_max_milliseconds`
等。
+此外还可以调节其他参数控制内存状态刷新和 GC，包括
`memory_gc_sleep_time_ms`，`soft_mem_limit_frac`，`memory_maintenance_sleep_time_ms`，`process_minor_gc_size`，`process_full_gc_size`，`thread_wait_gc_max_milliseconds`
等。
## 一些异常问题导致触发 OOM Killer
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/trouble-shooting/memory-management/memory-analysis/query-cancelled-after-query-memory-exceeded.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/trouble-shooting/memory-management/memory-analysis/query-cancelled-after-query-memory-exceeded.md
index 82b43a88572..262031de794 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/trouble-shooting/memory-management/memory-analysis/query-cancelled-after-query-memory-exceeded.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/admin-manual/trouble-shooting/memory-management/memory-analysis/query-cancelled-after-query-memory-exceeded.md
@@ -24,8 +24,6 @@ ERROR 1105 (HY000): errCode = 2, detailMessage =
(10.16.10.8)[MEM_LIMIT_EXCEEDED
`show variables;` 可以查看 Doris Session Veriable，其中的 `exec_mem_limit`
是单次查询和导入的执行内存限制，但从 Doris 1.2 开始支持查询内存超发
(overcommit)，旨在允许查询设置更灵活的内存限制，内存充足时即使查询内存超过上限也不会被
Cancel，所以通常用户无需关注查询内存使用。直到内存不足时，查询会在尝试分配新内存时等待一段时间，此时会基于一定规则优先 Cancel
`mem_used` 与 `exec_mem_limit` 比值大的
Query。如果等待过程中内存释放的大小满足需求，查询将继续执行，否则将抛出异常并终止查询。
-如果希望关闭查询内存超发，参考 [BE 配置项](../../../config/be-config)，在 `conf/be.conf` 中增加
`enable_query_memory_overcommit=false`，此时单次查询和导入的内存超过 `exec_mem_limit` 即会被
Cancel。如果你希望避免大查询对集群稳定性造成的负面影响，或者希望准确控制集群上的任务执行来保证足够的稳定性，那么可以考虑关闭查询内存超发。
-
## 查询内存分析
如果需要分析查询的内存使用，参考 [查询内存分析](./query-memory-analysis.md)。
diff --git a/versioned_docs/version-2.1/admin-manual/config/be-config.md
b/versioned_docs/version-2.1/admin-manual/config/be-config.md
index 955e942e19b..3b7937a0da5 100644
--- a/versioned_docs/version-2.1/admin-manual/config/be-config.md
+++ b/versioned_docs/version-2.1/admin-manual/config/be-config.md
@@ -1461,7 +1461,6 @@ This configuration is supported since the Apache Doris
1.2 version
* Default value: true
-
#### `enable_query_memory_overcommit`
* Description: If true, when the process does not exceed the soft mem limit,
the query memory will not be limited; when the process memory exceeds the soft
mem limit, the query with the largest ratio between the currently used memory
and the exec_mem_limit will be canceled. If false, cancel query when the memory
used exceeds exec_mem_limit.
diff --git a/versioned_docs/version-4.x/admin-manual/config/be-config.md
b/versioned_docs/version-4.x/admin-manual/config/be-config.md
index 2b7d66c28f3..81740d06a26 100644
--- a/versioned_docs/version-4.x/admin-manual/config/be-config.md
+++ b/versioned_docs/version-4.x/admin-manual/config/be-config.md
@@ -1322,11 +1322,6 @@ Indicates how many tablets failed to load in the data
directory. At the same tim
* Description: Whether enable simdjson to parse json while stream load
* Default value: true
-#### `enable_query_memory_overcommit`
-
-* Description: If true, when the process does not exceed the soft mem limit,
the query memory will not be limited; when the process memory exceeds the soft
mem limit, the query with the largest ratio between the currently used memory
and the exec_mem_limit will be canceled. If false, cancel query when the memory
used exceeds `exec_mem_limit`.
-* Default value: true
-
#### `user_files_secure_path`
* Description: The storage directory for files queried by `local` table valued
functions.
diff --git
a/versioned_docs/version-4.x/admin-manual/trouble-shooting/memory-management/memory-analysis/oom-crash-analysis.md
b/versioned_docs/version-4.x/admin-manual/trouble-shooting/memory-management/memory-analysis/oom-crash-analysis.md
index 1ba24d5aa25..1e9a0e8edc3 100644
---
a/versioned_docs/version-4.x/admin-manual/trouble-shooting/memory-management/memory-analysis/oom-crash-analysis.md
+++
b/versioned_docs/version-4.x/admin-manual/trouble-shooting/memory-management/memory-analysis/oom-crash-analysis.md
@@ -36,7 +36,7 @@ If the following phenomenon is met, it can be considered that
the cluster memory
At this time, refer to [BE Configuration Items](../../../config/be-config) to
reduce `mem_limit` and increase `max_sys_mem_available_low_water_mark_bytes` in
`be/conf/be.conf`. For more information about memory limits, watermark
calculation methods, and memory GC, see [Memory Control
Strategy](./../memory-feature/memory-control-strategy.md).
-In addition, other parameters can be adjusted to control memory status refresh
and GC, including `memory_gc_sleep_time_ms`, `soft_mem_limit_frac`,
`memory_maintenance_sleep_time_ms`, `process_minor_gc_size`,
`process_full_gc_size`, `enable_query_memory_overcommit`,
`thread_wait_gc_max_milliseconds`, etc.
+In addition, other parameters can be adjusted to control memory status refresh
and GC, including `memory_gc_sleep_time_ms`, `soft_mem_limit_frac`,
`memory_maintenance_sleep_time_ms`, `process_minor_gc_size`,
`process_full_gc_size`, `thread_wait_gc_max_milliseconds`, etc.
## Some abnormal problems trigger OOM Killer
diff --git
a/versioned_docs/version-4.x/admin-manual/trouble-shooting/memory-management/memory-analysis/query-cancelled-after-query-memory-exceeded.md
b/versioned_docs/version-4.x/admin-manual/trouble-shooting/memory-management/memory-analysis/query-cancelled-after-query-memory-exceeded.md
index c2cdf347c5b..cc92ceedf1b 100644
---
a/versioned_docs/version-4.x/admin-manual/trouble-shooting/memory-management/memory-analysis/query-cancelled-after-query-memory-exceeded.md
+++
b/versioned_docs/version-4.x/admin-manual/trouble-shooting/memory-management/memory-analysis/query-cancelled-after-query-memory-exceeded.md
@@ -24,8 +24,6 @@ The error message is divided into two parts:
`show variables;` You can view Doris Session Veriable, where `exec_mem_limit`
is the execution memory limit for a single query and load, but since Doris 1.2,
query memory over-issuance (overcommit) is supported, aiming to allow queries
to set more flexible memory limits. When there is sufficient memory, even if
the query memory exceeds the upper limit, it will not be Cancel, so users
usually do not need to pay attention to query memory usage. Until the memory is
insufficient, the query w [...]
-If you want to turn off query memory over-issuance, refer to [BE Configuration
Items](../../../config/be-config) and add
`enable_query_memory_overcommit=false` in `conf/be.conf`. At this time, a
single query and load memory exceeding `exec_mem_limit` will be canceled. If
you want to avoid the negative impact of large queries on cluster stability, or
want to accurately control the execution of tasks on the cluster to ensure
sufficient stability, then you can consider turning off query mem [...]
-
## Query Memory Analysis
If you need to analyze the memory usage of queries, refer to [Query Memory
Analysis](./query-memory-analysis.md).
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
