This is an automated email from the ASF dual-hosted git repository.
smiletan 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 238bb40ce2b [k8s][separation]separation persistent storage update
(#2772)
238bb40ce2b is described below
commit 238bb40ce2beb8bfcb692fa7148ad3280f3d0e43
Author: smiletan <[email protected]>
AuthorDate: Tue Aug 26 14:12:44 2025 +0800
[k8s][separation]separation persistent storage update (#2772)
## Versions
- [x] dev
- [x] 3.0
- [x] 2.1
- [ ] 2.0
## Languages
- [x] Chinese
- [x] English
## Docs Checklist
- [x] Checked by AI
- [ ] Test Cases Built
---
.../install-config-cluster.md | 4 +-
.../separating-storage-compute/config-cg.md | 85 ++++++-------
.../install-config-cluster.md | 4 +-
.../separating-storage-compute/config-cg.md | 131 +++++++++-----------
.../deploy-on-kubernetes/install-config-cluster.md | 2 +-
.../install-config-cluster.md | 4 +-
.../separating-storage-compute/config-cg.md | 136 +++++++++------------
.../deploy-on-kubernetes/install-config-cluster.md | 2 +-
.../install-config-cluster.md | 4 +-
.../separating-storage-compute/config-cg.md | 89 ++++++--------
10 files changed, 197 insertions(+), 264 deletions(-)
diff --git
a/docs/install/deploy-on-kubernetes/integrated-storage-compute/install-config-cluster.md
b/docs/install/deploy-on-kubernetes/integrated-storage-compute/install-config-cluster.md
index 7eb387b38a0..01b1f6fbce4 100644
---
a/docs/install/deploy-on-kubernetes/integrated-storage-compute/install-config-cluster.md
+++
b/docs/install/deploy-on-kubernetes/integrated-storage-compute/install-config-cluster.md
@@ -135,8 +135,6 @@ data:
syg_level = INFO
# NORMAL, BRIEF, ASYNC
syg_mode = ASYNC
- # sys_log_roll_num = 10
- # sys_log_verbose_modules = org.apache.doris
# audit_log_dir = $LOG_DIR
# audit_log_modules = slow_query, query
# audit_log_roll_num = 10
@@ -344,7 +342,7 @@ spec:
In the above configuration, ${your_storageclass} represents the name of the
StorageClass you want to use, and ${storageSize} represents the storage size
you want to allocation. The format of ${storageSize} follows the [quantity
expression](https://kubernetes.io/docs/reference/kubernetes-api/common-definitions/quantity/)
method of K8s, such as: 100Gi. Please replace them as needed when using.
:::tip Tip
-If you have reconfigured meta_dir or sys_log_dir in the [customized
configuration file](#custom-fe-startup-configuration), please reconfigure the
mountPath.
+If you have reconfigured meta_dir or `LOG_DIR` in the [customized
configuration file](#custom-fe-startup-configuration), please reconfigure the
mountPath.
:::
### Persistent storage for BE
diff --git
a/docs/install/deploy-on-kubernetes/separating-storage-compute/config-cg.md
b/docs/install/deploy-on-kubernetes/separating-storage-compute/config-cg.md
index 13c234004d4..4187ce0e2a5 100644
--- a/docs/install/deploy-on-kubernetes/separating-storage-compute/config-cg.md
+++ b/docs/install/deploy-on-kubernetes/separating-storage-compute/config-cg.md
@@ -157,62 +157,49 @@ The startup configuration must be mounted at the
`/etc/doris` directory.
:::
## Persistent Storage Configuration
-In the default deployment, the BE service uses Kubernetes
[`EmptyDir`](https://kubernetes.io/docs/concepts/storage/volumes/#emptydir) as
its cache. The EmptyDir mode is non-persistent; thus, cache data is lost upon
service restart, potentially reducing query performance. To ensure that cached
data is preserved after a restart and to maintain query performance, persistent
storage must be configured. The BE service logs are both output to the standard
output and written to the directory sp [...]
+In the default deployment, the BE service uses Kubernetes
[`EmptyDir`](https://kubernetes.io/docs/concepts/storage/volumes/#emptydir) as
its cache. EmptyDir is a non-persistent storage mode, meaning that cached data
is lost after the service restarts, which can reduce query performance.
-### Automatically Generating Persistent Storage with a Storage Template
-For compute group `cg1`, persistent storage for logs and cache data can be
configured using a storage template, as shown below:
-```yaml
-spec:
- computeGroups:
- - uniqueId: cg1
- persistentVolumes:
- - persistentVolumeClaimSpec:
- # storageClassName: ${storageclass_name}
- accessModes:
- - ReadWriteOnce
- resources:
- requests:
- storage: 500Gi
-```
-After deploying the cluster with this configuration, the Doris Operator
automatically mounts persistent storage for the log directory (default
`/opt/apache-doris/be/log`) and the cache directory (default
`/opt/apache-doris/be/file_cache`). If the log or cache directory is explicitly
specified in the [custom startup configuration](#custom-startup-configuration),
the Doris Operator will automatically parse and mount the persistent storage
accordingly. Persistent storage is implemented usin [...]
+To ensure that cached data is retained after service restarts and query
efficiency is not degraded, persistent storage should be configured for the
cache. The BE service logs are output both to standard output and to the
directory specified by the `LOG_DIR` parameter in the startup configuration. In
addition, the StreamLoad import process uses `/opt/apache-doris/be/storage` as
a temporary storage location. To prevent data loss caused by unexpected service
restarts, persistent storage sho [...]
-### Custom Mount Point Configuration
-The Doris Operator supports customized storage configurations for mount
points. The following example demonstrates a custom configuration for the log
directory:
+### Persistent Storage Example
+The following is an example configuration for mounting persistent storage to
the required data directories:
```yaml
spec:
computeGroups:
- - uniqueId: cg1
- persistentVolumes:
- - mountPaths:
- - /opt/apache-doris/be/log
- persistentVolumeClaimSpec:
- # storageClassName: ${storageclass_name}
- accessModes:
- - ReadWriteOnce
- resources:
- requests:
- storage: 300Gi
- - mountPaths:
- - /opt/apache-doris/be/storage
- persistentVolumeClaimSpec:
- # storageClassName: ${storageclass_name}
- accessModes:
- - ReadWriteOnce
- resources:
- requests:
- storage: 300Gi
- - persistentVolumeClaimSpec:
- # storageClassName: ${storageclass_name}
- accessModes:
- - ReadWriteOnce
- resources:
- requests:
- storage: 500Gi
+ - uniqueId: cg1
+ persistentVolumes:
+ - mountPaths:
+ - /opt/apache-doris/be/log
+ persistentVolumeClaimSpec:
+ # storageClassName: ${storageclass_name}
+ accessModes:
+ - ReadWriteOnce
+ resources:
+ requests:
+ storage: 300Gi
+ - mountPaths:
+ - /opt/apache-doris/be/storage
+ persistentVolumeClaimSpec:
+ # storageClassName: ${storageclass_name}
+ accessModes:
+ - ReadWriteOnce
+ resources:
+ requests:
+ storage: 300Gi
+ - persistentVolumeClaimSpec:
+ # storageClassName: ${storageclass_name}
+ accessModes:
+ - ReadWriteOnce
+ resources:
+ requests:
+ storage: 500Gi
```
-In the above configuration, the log directory is mounted using a custom
storage configuration with 300Gi, A 300Gi storage disk is mounted to the
directory `/opt/apache-doris/be/storage` used for WAL and StreamLoad imports,
etc. while the cache directory is mounted using the storage template with 500Gi.
+In this configuration, a 300Gi persistent volume is mounted to the log
directory using a custom storage configuration. Another 300Gi persistent volume
is mounted to the directory used for WAL and StreamLoad imports. The cache
directory is mounted with a 500Gi persistent volume created from a storage
template.
:::tip Note
-If the `mountPaths` array is empty, it indicates that the current storage
configuration is using the template configuration.
+- If the mountPaths array is left empty, the current storage configuration is
treated as a template. When users specify file_cache_path in the [startup
configuration](#custom-startup-configuration), the operator automatically
parses the directory path and mounts it.
+
+- It is recommended to configure four directories and mount four persistent
volumes to maximize cloud disk performance.
:::
### Disable Log Persistence
@@ -222,4 +209,4 @@ spec:
computeGroups:
- uniqueId: cg1
logNotStore: true
-```
\ No newline at end of file
+```
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/install/deploy-on-kubernetes/integrated-storage-compute/install-config-cluster.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/install/deploy-on-kubernetes/integrated-storage-compute/install-config-cluster.md
index cfc44ef06fe..47bec4222da 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/install/deploy-on-kubernetes/integrated-storage-compute/install-config-cluster.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/install/deploy-on-kubernetes/integrated-storage-compute/install-config-cluster.md
@@ -160,8 +160,6 @@ data:
syg_level = INFO
# NORMAL, BRIEF, ASYNC
syg_mode = ASYNC
- # sys_log_roll_num = 10
- # sys_log_verbose_modules = org.apache.doris
# audit_log_dir = $LOG_DIR
# audit_log_modules = slow_query, query
# audit_log_roll_num = 10
@@ -397,7 +395,7 @@ spec:
上述配置中，${your_storageclass} 表示希望使用的
[StorageClass](https://kubernetes.io/docs/concepts/storage/storage-classes/)
名称，${storageSize} 表示希望使用的存储大小，${storageSize} 的格式遵循 Kubernetes 的 [quantity
表达方式](https://kubernetes.io/docs/reference/kubernetes-api/common-definitions/quantity/),
比如：100Gi。
:::tip 提示
-如果在[定制化配置文件中](#fe-定制化启动配置)，重新设置了 `meta_dir` 或者 `sys_log_dir` 请重新设置 `mountPath`
。
+如果在[定制化配置文件中](#fe-定制化启动配置)，重新设置了 `meta_dir` 或者 `LOG_DIR` 请重新设置 `mountPath` 。
:::
### BE 持久化存储配置
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/install/deploy-on-kubernetes/separating-storage-compute/config-cg.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/install/deploy-on-kubernetes/separating-storage-compute/config-cg.md
index e3d270c9153..e1269de9e53 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/install/deploy-on-kubernetes/separating-storage-compute/config-cg.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/install/deploy-on-kubernetes/separating-storage-compute/config-cg.md
@@ -12,9 +12,9 @@
```yaml
spec:
computeGroups:
- - uniqueId: ${uniqueId}
- image: ${beImage}
- replicas: 1
+ - uniqueId: ${uniqueId}
+ image: ${beImage}
+ replicas: 1
```
`${beImage}` 为部署 BE 服务的镜像地址，请使用 [apache doris
官方镜像仓库](https://hub.docker.com/r/apache/doris)提供的镜像。`${uniqueId}`
为计算组的唯一标识也是计算组的名称，匹配规则为`[a-zA-Z][0-9a-zA-Z_]+`。replicas 为计算组内 BE 服务节点的数量。
@@ -23,12 +23,12 @@ spec:
```yaml
spec:
computeGroups:
- - uniqueId: cg1
- image: ${beImage}
- replicas: 3
- - uniqueId: cg2
- image: ${beImage}
- replicas: 2
+ - uniqueId: cg1
+ image: ${beImage}
+ replicas: 3
+ - uniqueId: cg2
+ image: ${beImage}
+ replicas: 2
```
其中，名称为 `cg1` 的计算组副本数为 3，名称为 `cg2` 的计算组副本数为 2。`${beImage}` 表示部署的 BE
服务镜像。尽管计算组之间相互独立，但建议同一存算分离集群中各计算组内 BE 服务所使用的镜像保持一致。
@@ -37,13 +37,13 @@ spec:
```yaml
spec:
computeGroups:
- - uniqueId: cg1
- requests:
- cpu: 8
- memory: 8Gi
- limits:
- cpu: 8
- memory: 8Gi
+ - uniqueId: cg1
+ requests:
+ cpu: 8
+ memory: 8Gi
+ limits:
+ cpu: 8
+ memory: 8Gi
```
将上述配置更新到需要部署的[`DorisDisaggregatedCluster`
资源](./install-doris-cluster.md#3-配置-dorisdisaggregatedcluster-资源)中。
@@ -81,12 +81,12 @@ test-disaggregated-cluster-cg1 ClusterIP
10.152.183.154 <none>
```yaml
spec:
computeGroups:
- - uniqueId: cg1
- service:
- type: NodePort
- portMaps:
- - nodePort: 31012
- targetPort: 8040
+ - uniqueId: cg1
+ service:
+ type: NodePort
+ portMaps:
+ - nodePort: 31012
+ targetPort: 8040
```
上述配置中，将计算组名称为 cg1 的 BE 监听端口 8040 映射到宿主机的 31012 端口。
#### 动态配置
@@ -94,9 +94,9 @@ spec:
```yaml
spec:
computeGroups:
- - uniqueId: cg1
- service:
- type: NodePort
+ - uniqueId: cg1
+ service:
+ type: NodePort
```
### LoadBalancer
@@ -152,57 +152,40 @@ spec:
## 持久化存储配置
默认部署中，BE 服务使用 Kubernetes 的
[EmptyDir](https://kubernetes.io/zh-cn/docs/concepts/storage/volumes/#emptydir)
作为服务的缓存。`EmptyDir` 模式是非持久化存储模式，服务重启后缓存的数据会丢失相应查询效率会降低。
-为了保证 BE 服务在重启后缓存数据不丢失、查询效率不降低，需要对缓存数据进行持久化存储。BE 服务的日志既会输出到标准输出，也会写入启动配置中
`LOG_DIR` 指定的目录，使用配置模板自动生成持久化存储时也会对日志数据进行持久化存储。
-### 使用存储模板自动生成
-对名称为 `cg1` 的计算组，使用存储模板对日志和缓存数据进行持久化配置，示例如下：
-```yaml
-spec:
- computeGroups:
- - uniqueId: cg1
- persistentVolumes:
- - persistentVolumeClaimSpec:
- # storageClassName: ${storageclass_name}
- accessModes:
- - ReadWriteOnce
- resources:
- requests:
- storage: 500Gi
-```
-使用如上配置部署集群后，Doris Operator 会自动为日志目录(默认为
`/opt/apache-doris/be/log`)以及缓存数据目录（默认为
`/opt/apache-doris/be/file_cache`）挂载持久化存储。
如果在[自定义启动配置](#自定义启动配置)中显示指定了日志存储目录或缓存目录，Doris Operator 会自动解析并进行挂载。
-持久化存储采用 [StorageClass
模式](https://kubernetes.io/docs/concepts/storage/storage-classes/)，可以通过
`storageClassName` 指定所需的 StorageClass。
+为了保证 BE 服务在重启后缓存数据不丢失、查询效率不降低，需要对缓存数据进行持久化存储。BE 服务的日志既会输出到标准输出，也会写入启动配置中
`LOG_DIR` 指定的目录。StreamLoad 模式导入会使用 `/opt/apache-doris/be/storage`
作为数据的暂存位置，避免服务异常重启后暂存的数据丢失，需要对对应写入位置挂载持久化存储。
-### 自定义挂载点配置
-Doris Operator 支持对挂载目录进行个性化存储配置。如下示例为日志目录设置个性化配置：
+### 持久化存储样例
+以下为需要持久化数据挂载持久化存储的配置样例：
```yaml
spec:
computeGroups:
- - uniqueId: cg1
- persistentVolumes:
- - mountPaths:
- - /opt/apache-doris/be/log
- persistentVolumeClaimSpec:
- # storageClassName: ${storageclass_name}
- accessModes:
- - ReadWriteOnce
- resources:
- requests:
- storage: 300Gi
- - mountPaths:
- - /opt/apache-doris/be/storage
- persistentVolumeClaimSpec:
- # storageClassName: ${storageclass_name}
- accessModes:
- - ReadWriteOnce
- resources:
- requests:
- storage: 300Gi
- - persistentVolumeClaimSpec:
- # storageClassName: ${storageclass_name}
- accessModes:
- - ReadWriteOnce
- resources:
- requests:
- storage: 500Gi
+ - uniqueId: cg1
+ persistentVolumes:
+ - mountPaths:
+ - /opt/apache-doris/be/log
+ persistentVolumeClaimSpec:
+ # storageClassName: ${storageclass_name}
+ accessModes:
+ - ReadWriteOnce
+ resources:
+ requests:
+ storage: 300Gi
+ - mountPaths:
+ - /opt/apache-doris/be/storage
+ persistentVolumeClaimSpec:
+ # storageClassName: ${storageclass_name}
+ accessModes:
+ - ReadWriteOnce
+ resources:
+ requests:
+ storage: 300Gi
+ - persistentVolumeClaimSpec:
+ # storageClassName: ${storageclass_name}
+ accessModes:
+ - ReadWriteOnce
+ resources:
+ requests:
+ storage: 500Gi
```
上述配置中，日志目录使用自定义的存储配置挂载 300Gi 的存储磁盘，WAL 以及 StreamLoad 导入时使用的目录配置挂载 300Gi
的存储磁盘，而缓存目录则使用存储模板挂载 500Gi 的存储磁盘。
@@ -215,6 +198,6 @@ spec:
```yaml
spec:
computeGroups:
- - uniqueId: cg1
- logNotStore: true
+ - uniqueId: cg1
+ logNotStore: true
```
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/install/deploy-on-kubernetes/install-config-cluster.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/install/deploy-on-kubernetes/install-config-cluster.md
index 2e658c8156d..0f514cae975 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/install/deploy-on-kubernetes/install-config-cluster.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/install/deploy-on-kubernetes/install-config-cluster.md
@@ -329,7 +329,7 @@ spec:
上述配置中，${your_storageclass} 表示希望使用的
[StorageClass](https://kubernetes.io/docs/concepts/storage/storage-classes/)
名称，${storageSize} 表示希望使用的存储大小，${storageSize} 的格式遵循 Kubernetes 的 [quantity
表达方式](https://kubernetes.io/docs/reference/kubernetes-api/common-definitions/quantity/),
比如：100Gi。
:::tip 提示
-如果在[定制化配置文件中](#fe-定制化启动配置)，重新设置了 `meta_dir` 或者 `sys_log_dir` 请重新设置 `mountPath`
。
+如果在[定制化配置文件中](#fe-定制化启动配置)，重新设置了 `meta_dir` 或者 `LOG_DIR` 请重新设置 `mountPath` 。
:::
### BE 持久化存储配置
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/install/deploy-on-kubernetes/integrated-storage-compute/install-config-cluster.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/install/deploy-on-kubernetes/integrated-storage-compute/install-config-cluster.md
index 07af69e1c66..e08c1023663 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/install/deploy-on-kubernetes/integrated-storage-compute/install-config-cluster.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/install/deploy-on-kubernetes/integrated-storage-compute/install-config-cluster.md
@@ -160,8 +160,6 @@ data:
syg_level = INFO
# NORMAL, BRIEF, ASYNC
syg_mode = ASYNC
- # sys_log_roll_num = 10
- # sys_log_verbose_modules = org.apache.doris
# audit_log_dir = $LOG_DIR
# audit_log_modules = slow_query, query
# audit_log_roll_num = 10
@@ -397,7 +395,7 @@ spec:
上述配置中，${your_storageclass} 表示希望使用的
[StorageClass](https://kubernetes.io/docs/concepts/storage/storage-classes/)
名称，${storageSize} 表示希望使用的存储大小，${storageSize} 的格式遵循 Kubernetes 的 [quantity
表达方式](https://kubernetes.io/docs/reference/kubernetes-api/common-definitions/quantity/),
比如：100Gi。
:::tip 提示
-如果在[定制化配置文件中](#fe-定制化启动配置)，重新设置了 `meta_dir` 或者 `sys_log_dir`请重新设置 `mountPath` 。
+如果在[定制化配置文件中](#fe-定制化启动配置)，重新设置了 `meta_dir` 或者 `LOG_DIR`请重新设置 `mountPath` 。
:::
### BE 持久化存储配置
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/install/deploy-on-kubernetes/separating-storage-compute/config-cg.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/install/deploy-on-kubernetes/separating-storage-compute/config-cg.md
index 41a83036650..86d01763dc1 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/install/deploy-on-kubernetes/separating-storage-compute/config-cg.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/install/deploy-on-kubernetes/separating-storage-compute/config-cg.md
@@ -12,9 +12,9 @@
```yaml
spec:
computeGroups:
- - uniqueId: ${uniqueId}
- image: ${beImage}
- replicas: 1
+ - uniqueId: ${uniqueId}
+ image: ${beImage}
+ replicas: 1
```
`${beImage}` 为部署 BE 服务的镜像地址，请使用 [apache doris
官方镜像仓库](https://hub.docker.com/r/apache/doris)提供的镜像。`${uniqueId}`
为计算组的唯一标识也是计算组的名称，匹配规则为`[a-zA-Z][0-9a-zA-Z_]+`。replicas 为计算组内 BE 服务节点的数量。
@@ -23,12 +23,12 @@ spec:
```yaml
spec:
computeGroups:
- - uniqueId: cg1
- image: ${beImage}
- replicas: 3
- - uniqueId: cg2
- image: ${beImage}
- replicas: 2
+ - uniqueId: cg1
+ image: ${beImage}
+ replicas: 3
+ - uniqueId: cg2
+ image: ${beImage}
+ replicas: 2
```
其中，名称为 `cg1` 的计算组副本数为 3，名称为 `cg2` 的计算组副本数为 2。`${beImage}` 表示部署的 BE
服务镜像。尽管计算组之间相互独立，但建议同一存算分离集群中各计算组内 BE 服务所使用的镜像保持一致。
@@ -37,13 +37,13 @@ spec:
```yaml
spec:
computeGroups:
- - uniqueId: cg1
- requests:
- cpu: 8
- memory: 8Gi
- limits:
- cpu: 8
- memory: 8Gi
+ - uniqueId: cg1
+ requests:
+ cpu: 8
+ memory: 8Gi
+ limits:
+ cpu: 8
+ memory: 8Gi
```
将上述配置更新到需要部署的[`DorisDisaggregatedCluster`
资源](./install-doris-cluster.md#3-配置-dorisdisaggregatedcluster-资源)中。
@@ -81,12 +81,12 @@ test-disaggregated-cluster-cg1 ClusterIP
10.152.183.154 <none>
```yaml
spec:
computeGroups:
- - uniqueId: cg1
- service:
- type: NodePort
- portMaps:
- - nodePort: 31012
- targetPort: 8040
+ - uniqueId: cg1
+ service:
+ type: NodePort
+ portMaps:
+ - nodePort: 31012
+ targetPort: 8040
```
上述配置中，将计算组名称为 cg1 的 BE 监听端口 8040 映射到宿主机的 31012 端口。
#### 动态配置
@@ -94,9 +94,9 @@ spec:
```yaml
spec:
computeGroups:
- - uniqueId: cg1
- service:
- type: NodePort
+ - uniqueId: cg1
+ service:
+ type: NodePort
```
### LoadBalancer
@@ -126,7 +126,7 @@ spec:
be.conf: |
# For jdk 17, this JAVA_OPTS will be used as default JVM options
JAVA_OPTS_FOR_JDK_17="-Xmx1024m -DlogPath=$LOG_DIR/jni.log
-Xlog:gc*:$LOG_DIR/be.gc.log.$CUR_DATE:time,uptime:filecount=10,filesize=50M
-Djavax.security.auth.useSubjectCredsOnly=false -Dsun.security.krb5.debug=true
-Dsun.java.command=DorisBE -XX:-CriticalJNINatives
-XX:+IgnoreUnrecognizedVMOptions --add-opens=java.base/java.lang=ALL-UNNAMED
--add-opens=java.base/java.lang.invoke=ALL-UNNAMED
--add-opens=java.base/java.lang.reflect=ALL-UNNAMED
--add-opens=java.base/java.io=ALL-UNNA [...]
- file_cache_path =
[{"path":"/opt/apache-doris/be/file_cache","total_size":107374182400,"query_limit":107374182400}]
+ file_cache_path =
[{"path":"/mnt/apache-doris/be/file_cache","total_size":107374182400,"query_limit":107374182400}]
```
存算分离集群 BE 服务的启动配置必须设置 `file_cache_path`，格式请参考[存算分离配置
`be.conf`](../../../compute-storage-decoupled/compilation-and-deployment.md#541-配置-beconf)
章节。
2. 部署 ConfigMap
@@ -152,62 +152,46 @@ spec:
## 持久化存储配置
默认部署中，BE 服务使用 Kubernetes 的
[EmptyDir](https://kubernetes.io/zh-cn/docs/concepts/storage/volumes/#emptydir)
作为服务的缓存。`EmptyDir` 模式是非持久化存储模式，服务重启后缓存的数据会丢失相应查询效率会降低。
-为了保证 BE 服务在重启后缓存数据不丢失、查询效率不降低，需要对缓存数据进行持久化存储。BE 服务的日志既会输出到标准输出，也会写入启动配置中
`LOG_DIR` 指定的目录，使用配置模板自动生成持久化存储时也会对日志数据进行持久化存储。
-### 使用存储模板自动生成
-对名称为 `cg1` 的计算组，使用存储模板对日志和缓存数据进行持久化配置，示例如下：
-```yaml
-spec:
- computeGroups:
- - uniqueId: cg1
- persistentVolumes:
- - persistentVolumeClaimSpec:
- # storageClassName: ${storageclass_name}
- accessModes:
- - ReadWriteOnce
- resources:
- requests:
- storage: 500Gi
-```
-使用如上配置部署集群后，Doris Operator 会自动为日志目录(默认为
`/opt/apache-doris/be/log`)以及缓存数据目录（默认为
`/opt/apache-doris/be/file_cache`）挂载持久化存储。
如果在[自定义启动配置](#自定义启动配置)中显示指定了日志存储目录或缓存目录，Doris Operator 会自动解析并进行挂载。
-持久化存储采用 [StorageClass
模式](https://kubernetes.io/docs/concepts/storage/storage-classes/)，可以通过
`storageClassName` 指定所需的 StorageClass。
+为了保证 BE 服务在重启后缓存数据不丢失、查询效率不降低，需要对缓存数据进行持久化存储。BE 服务的日志既会输出到标准输出，也会写入启动配置中
`LOG_DIR` 指定的目录。StreamLoad 模式导入会使用 `/opt/apache-doris/be/storage`
作为数据的暂存位置，避免服务异常重启后暂存的数据丢失，需要对对应写入位置挂载持久化存储。
-### 自定义挂载点配置
-Doris Operator 支持对挂载目录进行个性化存储配置。如下示例为日志目录设置个性化配置：
+### 持久化存储样例
+以下为需要持久化数据挂载持久化存储的配置样例：
```yaml
spec:
computeGroups:
- - uniqueId: cg1
- persistentVolumes:
- - mountPaths:
- - /opt/apache-doris/be/log
- persistentVolumeClaimSpec:
- # storageClassName: ${storageclass_name}
- accessModes:
- - ReadWriteOnce
- resources:
- requests:
- storage: 300Gi
- - mountPaths:
- - /opt/apache-doris/be/storage
- persistentVolumeClaimSpec:
- # storageClassName: ${storageclass_name}
- accessModes:
- - ReadWriteOnce
- resources:
- requests:
- storage: 300Gi
- - persistentVolumeClaimSpec:
- # storageClassName: ${storageclass_name}
- accessModes:
- - ReadWriteOnce
- resources:
- requests:
- storage: 500Gi
+ - uniqueId: cg1
+ persistentVolumes:
+ - mountPaths:
+ - /opt/apache-doris/be/log
+ persistentVolumeClaimSpec:
+ # storageClassName: ${storageclass_name}
+ accessModes:
+ - ReadWriteOnce
+ resources:
+ requests:
+ storage: 300Gi
+ - mountPaths:
+ - /opt/apache-doris/be/storage
+ persistentVolumeClaimSpec:
+ # storageClassName: ${storageclass_name}
+ accessModes:
+ - ReadWriteOnce
+ resources:
+ requests:
+ storage: 300Gi
+ - persistentVolumeClaimSpec:
+ # storageClassName: ${storageclass_name}
+ accessModes:
+ - ReadWriteOnce
+ resources:
+ requests:
+ storage: 500Gi
```
上述配置中，日志目录使用自定义的存储配置挂载 300Gi 的存储磁盘，WAL 以及 StreamLoad 导入时使用的目录配置挂载 300Gi
的存储磁盘，而缓存目录则使用存储模板挂载 500Gi 的存储磁盘。
:::tip 提示
-若 `mountPaths` 数组为空，则表示当前存储配置为模板配置。
+- 若 `mountPaths` 数组为空，则表示当前存储配置为模板配置。当用户在[启动配置](#自定义启动配置)中配置了
`file_cache_path`, operator 会自动解析出目录地址进行挂载。
+- 推荐配置 4 个目录，挂载 4 个持久化存储来发挥云盘的最大效应。
:::
### 不持久化日志
@@ -215,6 +199,6 @@ spec:
```yaml
spec:
computeGroups:
- - uniqueId: cg1
- logNotStore: true
+ - uniqueId: cg1
+ logNotStore: true
```
diff --git
a/versioned_docs/version-2.1/install/deploy-on-kubernetes/install-config-cluster.md
b/versioned_docs/version-2.1/install/deploy-on-kubernetes/install-config-cluster.md
index 55a3e20ae36..deda28f5e5f 100644
---
a/versioned_docs/version-2.1/install/deploy-on-kubernetes/install-config-cluster.md
+++
b/versioned_docs/version-2.1/install/deploy-on-kubernetes/install-config-cluster.md
@@ -267,7 +267,7 @@ spec:
In the above configuration, ${your_storageclass} represents the name of the
StorageClass you want to use, and ${storageSize} represents the storage size
you want to allocation. The format of ${storageSize} follows the [quantity
expression](https://kubernetes.io/docs/reference/kubernetes-api/common-definitions/quantity/)
method of K8s, such as: 100Gi. Please replace them as needed when using.
:::tip Tip
-If you have reconfigured meta_dir or sys_log_dir in the [customized
configuration file](#custom-fe-startup-configuration), please reconfigure the
mountPath.
+If you have reconfigured meta_dir or `LOG_DIR` in the [customized
configuration file](#custom-fe-startup-configuration), please reconfigure the
mountPath.
:::
### Persistent storage for BE
diff --git
a/versioned_docs/version-3.0/install/deploy-on-kubernetes/integrated-storage-compute/install-config-cluster.md
b/versioned_docs/version-3.0/install/deploy-on-kubernetes/integrated-storage-compute/install-config-cluster.md
index b1d52b5ebf5..3001b638c34 100644
---
a/versioned_docs/version-3.0/install/deploy-on-kubernetes/integrated-storage-compute/install-config-cluster.md
+++
b/versioned_docs/version-3.0/install/deploy-on-kubernetes/integrated-storage-compute/install-config-cluster.md
@@ -135,8 +135,6 @@ data:
syg_level = INFO
# NORMAL, BRIEF, ASYNC
syg_mode = ASYNC
- # sys_log_roll_num = 10
- # sys_log_verbose_modules = org.apache.doris
# audit_log_dir = $LOG_DIR
# audit_log_modules = slow_query, query
# audit_log_roll_num = 10
@@ -344,7 +342,7 @@ spec:
In the above configuration, ${your_storageclass} represents the name of the
StorageClass you want to use, and ${storageSize} represents the storage size
you want to allocation. The format of ${storageSize} follows the [quantity
expression](https://kubernetes.io/docs/reference/kubernetes-api/common-definitions/quantity/)
method of K8s, such as: 100Gi. Please replace them as needed when using.
:::tip Tip
-If you have reconfigured meta_dir or sys_log_dir in the [customized
configuration file](#custom-fe-startup-configuration), please reconfigure the
mountPath.
+If you have reconfigured meta_dir or `LOG_DIR` in the [customized
configuration file](#custom-fe-startup-configuration), please reconfigure the
mountPath.
:::
### Persistent storage for BE
diff --git
a/versioned_docs/version-3.0/install/deploy-on-kubernetes/separating-storage-compute/config-cg.md
b/versioned_docs/version-3.0/install/deploy-on-kubernetes/separating-storage-compute/config-cg.md
index d79a6ce8020..f5d6ca5625e 100644
---
a/versioned_docs/version-3.0/install/deploy-on-kubernetes/separating-storage-compute/config-cg.md
+++
b/versioned_docs/version-3.0/install/deploy-on-kubernetes/separating-storage-compute/config-cg.md
@@ -157,62 +157,49 @@ The startup configuration must be mounted at the
`/etc/doris` directory.
:::
## Persistent Storage Configuration
-In the default deployment, the BE service uses Kubernetes
[`EmptyDir`](https://kubernetes.io/docs/concepts/storage/volumes/#emptydir) as
its cache. The EmptyDir mode is non-persistent; thus, cache data is lost upon
service restart, potentially reducing query performance. To ensure that cached
data is preserved after a restart and to maintain query performance, persistent
storage must be configured. The BE service logs are both output to the standard
output and written to the directory sp [...]
+In the default deployment, the BE service uses Kubernetes
[`EmptyDir`](https://kubernetes.io/docs/concepts/storage/volumes/#emptydir) as
its cache. EmptyDir is a non-persistent storage mode, meaning that cached data
is lost after the service restarts, which can reduce query performance.
-### Automatically Generating Persistent Storage with a Storage Template
-For compute group `cg1`, persistent storage for logs and cache data can be
configured using a storage template, as shown below:
-```yaml
-spec:
- computeGroups:
- - uniqueId: cg1
- persistentVolumes:
- - persistentVolumeClaimSpec:
- # storageClassName: ${storageclass_name}
- accessModes:
- - ReadWriteOnce
- resources:
- requests:
- storage: 500Gi
-```
-After deploying the cluster with this configuration, the Doris Operator
automatically mounts persistent storage for the log directory (default
`/opt/apache-doris/be/log`) and the cache directory (default
`/opt/apache-doris/be/file_cache`). If the log or cache directory is explicitly
specified in the [custom startup configuration](#custom-startup-configuration),
the Doris Operator will automatically parse and mount the persistent storage
accordingly. Persistent storage is implemented usin [...]
+To ensure that cached data is retained after service restarts and query
efficiency is not degraded, persistent storage should be configured for the
cache. The BE service logs are output both to standard output and to the
directory specified by the `LOG_DIR` parameter in the startup configuration. In
addition, the StreamLoad import process uses `/opt/apache-doris/be/storage` as
a temporary storage location. To prevent data loss caused by unexpected service
restarts, persistent storage sho [...]
-### Custom Mount Point Configuration
-The Doris Operator supports customized storage configurations for mount
points. The following example demonstrates a custom configuration for the log
directory:
+### Persistent Storage Example
+The following is an example configuration for mounting persistent storage to
the required data directories:
```yaml
spec:
computeGroups:
- - uniqueId: cg1
- persistentVolumes:
- - mountPaths:
- - /opt/apache-doris/be/log
- persistentVolumeClaimSpec:
- # storageClassName: ${storageclass_name}
- accessModes:
- - ReadWriteOnce
- resources:
- requests:
- storage: 300Gi
- - mountPaths:
- - /opt/apache-doris/be/storage
- persistentVolumeClaimSpec:
- # storageClassName: ${storageclass_name}
- accessModes:
- - ReadWriteOnce
- resources:
- requests:
- storage: 300Gi
- - persistentVolumeClaimSpec:
- # storageClassName: ${storageclass_name}
- accessModes:
- - ReadWriteOnce
- resources:
- requests:
- storage: 500Gi
+ - uniqueId: cg1
+ persistentVolumes:
+ - mountPaths:
+ - /opt/apache-doris/be/log
+ persistentVolumeClaimSpec:
+ # storageClassName: ${storageclass_name}
+ accessModes:
+ - ReadWriteOnce
+ resources:
+ requests:
+ storage: 300Gi
+ - mountPaths:
+ - /opt/apache-doris/be/storage
+ persistentVolumeClaimSpec:
+ # storageClassName: ${storageclass_name}
+ accessModes:
+ - ReadWriteOnce
+ resources:
+ requests:
+ storage: 300Gi
+ - persistentVolumeClaimSpec:
+ # storageClassName: ${storageclass_name}
+ accessModes:
+ - ReadWriteOnce
+ resources:
+ requests:
+ storage: 500Gi
```
-In the above configuration, the log directory is mounted using a custom
storage configuration with 300Gi, A 300Gi storage disk is mounted to the
directory `/opt/apache-doris/be/storage` used for WAL and StreamLoad imports,
etc. while the cache directory is mounted using the storage template with 500Gi.
+In this configuration, a 300Gi persistent volume is mounted to the log
directory using a custom storage configuration. Another 300Gi persistent volume
is mounted to the directory used for WAL and StreamLoad imports. The cache
directory is mounted with a 500Gi persistent volume created from a storage
template.
:::tip Note
-If the `mountPaths` array is empty, it indicates that the current storage
configuration is using the template configuration.
+- If the mountPaths array is left empty, the current storage configuration is
treated as a template. When users specify file_cache_path in the [startup
configuration](#custom-startup-configuration), the operator automatically
parses the directory path and mounts it.
+
+- It is recommended to configure four directories and mount four persistent
volumes to maximize cloud disk performance.
:::
### Disable Log Persistence
@@ -220,6 +207,6 @@ If log persistence is not required and logs should only be
output to the standar
```yaml
spec:
computeGroups:
- - uniqueId: cg1
- logNotStore: true
-```
\ No newline at end of file
+ - uniqueId: cg1
+ logNotStore: true
+```
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
