You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by zh...@apache.org on 2022/01/07 05:31:14 UTC
[dolphinscheduler-website] branch master updated: Remove logger server (#620)
This is an automated email from the ASF dual-hosted git repository.
zhongjiajie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/dolphinscheduler-website.git
The following commit(s) were added to refs/heads/master by this push:
new f19d877 Remove logger server (#620)
f19d877 is described below
commit f19d8770a0b3cdbfe04b2da67bb5970e0d8220d1
Author: Aaron Lin <15...@qq.com>
AuthorDate: Fri Jan 7 13:28:01 2022 +0800
Remove logger server (#620)
* Remove logger server
* Update development/zh-cn/development-environment-setup.md
Co-authored-by: Jiajie Zhong <zh...@gmail.com>
---
development/en-us/architecture-design.md | 1 -
development/en-us/development-environment-setup.md | 5 ++---
development/zh-cn/architecture-design.md | 2 --
development/zh-cn/development-environment-setup.md | 5 ++---
docs/en-us/dev/user_doc/architecture/design.md | 2 --
docs/en-us/dev/user_doc/dev_run.md | 2 +-
docs/en-us/dev/user_doc/expansion-reduction.md | 13 +++----------
docs/en-us/dev/user_doc/guide/installation/docker.md | 11 ++---------
docs/en-us/dev/user_doc/guide/installation/kubernetes.md | 1 -
.../en-us/dev/user_doc/guide/installation/pseudo-cluster.md | 6 +-----
docs/zh-cn/dev/user_doc/architecture/design.md | 2 --
docs/zh-cn/dev/user_doc/expansion-reduction.md | 13 +++----------
docs/zh-cn/dev/user_doc/guide/installation/docker.md | 11 ++---------
docs/zh-cn/dev/user_doc/guide/installation/kubernetes.md | 1 -
.../zh-cn/dev/user_doc/guide/installation/pseudo-cluster.md | 6 +-----
15 files changed, 17 insertions(+), 64 deletions(-)
diff --git a/development/en-us/architecture-design.md b/development/en-us/architecture-design.md
index 5ddf602..75d207b 100644
--- a/development/en-us/architecture-design.md
+++ b/development/en-us/architecture-design.md
@@ -76,7 +76,6 @@ Before explaining the architecture of the schedule system, let us first understa
##### This service contains:
- **FetchTaskThread** is mainly responsible for continuously receiving tasks from **Task Queue** and calling **TaskScheduleThread** corresponding executors according to different task types.
- - **LoggerServer** is an RPC service that provides functions such as log fragment viewing, refresh and download.
- **ZooKeeper**
diff --git a/development/en-us/development-environment-setup.md b/development/en-us/development-environment-setup.md
index 5d5ae57..415ba2e 100644
--- a/development/en-us/development-environment-setup.md
+++ b/development/en-us/development-environment-setup.md
@@ -25,7 +25,7 @@ git clone git@github.com:apache/dolphinscheduler.git
There are two ways to configure the DolphinScheduler development environment, standalone mode and normal mode
* [Standalone mode](#dolphinscheduler-standalone-quick-start): **Recommended**，more convenient to build development environment, it can cover most scenes.
-* [Normal mode](#dolphinscheduler-normal-mode): Separate server master, worker, api, logger, which can cover more test environments than standalone, and it is more like production environment in real life.
+* [Normal mode](#dolphinscheduler-normal-mode): Separate server master, worker, api, which can cover more test environments than standalone, and it is more like production environment in real life.
## DolphinScheduler Standalone Quick Start
@@ -132,12 +132,11 @@ Following steps will guide how to start the DolphinScheduler backend service
##### Server start
-There are three necessary server we have to start, including MasterServer，WorkerServer，ApiApplicationServer, and a optional server you could start if you need, named LoggerServer.
+There are three services that need to be started, including MasterServer, WorkerServer, ApiApplicationServer.
* MasterServer：Execute function `main` in the class `org.apache.dolphinscheduler.server.master.MasterServer` by Intellij IDEA, with the configuration *VM Options* `-Dlogging.config=classpath:logback-master.xml -Ddruid.mysql.usePingMethod=false -Dspring.profiles.active=mysql`
* WorkerServer：Execute function `main` in the class `org.apache.dolphinscheduler.server.worker.WorkerServer` by Intellij IDEA, with the configuration *VM Options* `-Dlogging.config=classpath:logback-worker.xml -Ddruid.mysql.usePingMethod=false -Dspring.profiles.active=mysql`
* ApiApplicationServer：Execute function `main` in the class `org.apache.dolphinscheduler.api.ApiApplicationServer` by Intellij IDEA, with the configuration *VM Options* `-Dlogging.config=classpath:logback-api.xml -Dspring.profiles.active=api,mysql`. After it started, you could find Open API documentation in http://localhost:12345/dolphinscheduler/doc.html
-* LoggerServer：**Optional server, only start if you need**，Execute function `main` in the class `org.apache.dolphinscheduler.server.log.LoggerServer` by Intellij IDEA
> The `mysql` in the VM Options `-Dspring.profiles.active=mysql` means specified configuration file
diff --git a/development/zh-cn/architecture-design.md b/development/zh-cn/architecture-design.md
index e989882..0a6fcbb 100644
--- a/development/zh-cn/architecture-design.md
+++ b/development/zh-cn/architecture-design.md
@@ -66,8 +66,6 @@
##### 该服务包含：
- **FetchTaskThread**主要负责不断从**Task Queue**中领取任务，并根据不同任务类型调用**TaskScheduleThread**对应执行器。
- - **LoggerServer**是一个RPC服务，提供日志分片查看、刷新和下载等功能
-
* **ZooKeeper**
ZooKeeper服务，系统中的MasterServer和WorkerServer节点都通过ZooKeeper来进行集群管理和容错。另外系统还基于ZooKeeper进行事件监听和分布式锁。
diff --git a/development/zh-cn/development-environment-setup.md b/development/zh-cn/development-environment-setup.md
index aa40993..d8851cd 100644
--- a/development/zh-cn/development-environment-setup.md
+++ b/development/zh-cn/development-environment-setup.md
@@ -24,7 +24,7 @@ git clone git@github.com:apache/dolphinscheduler.git
DolphinScheduler 开发环境配置有两个方式，分别是standalone模式，以及普通模式
* [standalone模式](#dolphinscheduler-standalone快速开发模式)：**推荐使用，但仅支持 1.3.9 及以后的版本**，方便快速的开发环境搭建，能解决大部分场景的开发
-* [普通模式](#dolphinscheduler-普通开发模式)：master、worker、api、logger等单独启动，能更好的的模拟真实生产环境，可以覆盖的测试环境更多
+* [普通模式](#dolphinscheduler-普通开发模式)：master、worker、api等单独启动，能更好的的模拟真实生产环境，可以覆盖的测试环境更多
## DolphinScheduler Standalone快速开发模式
@@ -129,12 +129,11 @@ DolphinScheduler 的元数据存储在关系型数据库中，目前支持的关
##### 启动服务
-我们需要启动三个必须服务，包括 MasterServer，WorkerServer，ApiApplicationServer，如果有需求可以启动可选服务 LoggerServer
+我们需要启动三个服务，包括 MasterServer，WorkerServer，ApiApplicationServer
* MasterServer：在 Intellij IDEA 中执行 `org.apache.dolphinscheduler.server.master.MasterServer` 中的 `main` 方法，并配置 *VM Options* `-Dlogging.config=classpath:logback-master.xml -Ddruid.mysql.usePingMethod=false -Dspring.profiles.active=mysql`
* WorkerServer：在 Intellij IDEA 中执行 `org.apache.dolphinscheduler.server.worker.WorkerServer` 中的 `main` 方法，并配置 *VM Options* `-Dlogging.config=classpath:logback-worker.xml -Ddruid.mysql.usePingMethod=false -Dspring.profiles.active=mysql`
* ApiApplicationServer：在 Intellij IDEA 中执行 `org.apache.dolphinscheduler.api.ApiApplicationServer` 中的 `main` 方法，并配置 *VM Options* `-Dlogging.config=classpath:logback-api.xml -Dspring.profiles.active=api,mysql`。启动完成可以浏览 Open API 文档，地址为 http://localhost:12345/dolphinscheduler/doc.html
-* LoggerServer：**这是非必须功能，可以不开启**，在 Intellij IDEA 中执行 `org.apache.dolphinscheduler.server.log.LoggerServer` 中的 `main` 方法
> VM Options `-Dspring.profiles.active=mysql` 中 `mysql` 表示指定的配置文件
diff --git a/docs/en-us/dev/user_doc/architecture/design.md b/docs/en-us/dev/user_doc/architecture/design.md
index c2c89c9..21677ca 100644
--- a/docs/en-us/dev/user_doc/architecture/design.md
+++ b/docs/en-us/dev/user_doc/architecture/design.md
@@ -78,8 +78,6 @@ Before explaining the architecture of the scheduling system, let's first underst
##### The service mainly includes:
- **Fetch TaskThread** is mainly responsible for continuously getting tasks from **Task Queue**, and calling **TaskScheduleThread** corresponding executor according to different task types.
- - **LoggerServer** is an RPC service that provides functions such as log fragment viewing, refreshing and downloading
-
* **ZooKeeper**
ZooKeeper service, MasterServer and WorkerServer nodes in the system all use ZooKeeper for cluster management and fault tolerance. In addition, the system is based on ZooKeeper for event monitoring and distributed locks.
diff --git a/docs/en-us/dev/user_doc/dev_run.md b/docs/en-us/dev/user_doc/dev_run.md
index df823bd..afebd02 100644
--- a/docs/en-us/dev/user_doc/dev_run.md
+++ b/docs/en-us/dev/user_doc/dev_run.md
@@ -100,7 +100,7 @@ Run the main method of org.apache.dolphinscheduler.api.ApiApplicationServer. You
-Dlogging.config=classpath:logback-api.xml -Dspring.profiles.active=api
```
-xi. If you need to use the log function, execute the main method of org.apache.dolphinscheduler.server.log.LoggerServer.
+xi. LoggerServer is already integrated into the Master and Worker, so there is no need to start them independently
xii. Backend swagger address: http://localhost:12345/dolphinscheduler/doc.html?language=zh_CN&lang=cn
diff --git a/docs/en-us/dev/user_doc/expansion-reduction.md b/docs/en-us/dev/user_doc/expansion-reduction.md
index 365d496..301a623 100644
--- a/docs/en-us/dev/user_doc/expansion-reduction.md
+++ b/docs/en-us/dev/user_doc/expansion-reduction.md
@@ -135,7 +135,6 @@ bin/stop-all.sh # stop all services
sh bin/dolphinscheduler-daemon.sh stop master-server # stop master service
sh bin/dolphinscheduler-daemon.sh stop worker-server # stop worker service
-sh bin/dolphinscheduler-daemon.sh stop logger-server # stop logger service
sh bin/dolphinscheduler-daemon.sh stop api-server # stop api service
sh bin/dolphinscheduler-daemon.sh stop alert-server # stop alert service
@@ -145,7 +144,6 @@ bin/start-all.sh # start all services
sh bin/dolphinscheduler-daemon.sh start master-server # start master service
sh bin/dolphinscheduler-daemon.sh start worker-server # start worker service
-sh bin/dolphinscheduler-daemon.sh start logger-server # start logger service
sh bin/dolphinscheduler-daemon.sh start api-server # start api service
sh bin/dolphinscheduler-daemon.sh start alert-server # start alert service
@@ -161,7 +159,6 @@ sh bin/dolphinscheduler-daemon.sh start alert-server # start alert service
```
MasterServer ----- master service
WorkerServer ----- worker service
- LoggerServer ----- logger service
ApiApplicationServer ----- api service
AlertServer ----- alert service
```
@@ -172,9 +169,8 @@ After successful startup, you can view the logs, which are stored in the logs fo
logs/
├── dolphinscheduler-alert-server.log
├── dolphinscheduler-master-server.log
- |—— dolphinscheduler-worker-server.log
- |—— dolphinscheduler-api-server.log
- |—— dolphinscheduler-logger-server.log
+ ├── dolphinscheduler-worker-server.log
+ ├── dolphinscheduler-api-server.log
```
If the above services are started normally and the scheduling system page is normal, check whether there is an expanded Master or Worker service in the [Monitor] of the web system. If it exists, the expansion is complete.
@@ -186,7 +182,7 @@ There are two steps for shrinking. After performing the following two steps, the
### 2.1 Stop the service on the scaled-down node
* If you are scaling down the master node, identify the physical machine where the master service is located, and stop the master service on the physical machine.
- * If the worker node is scaled down, determine the physical machine where the worker service is to be scaled down and stop the worker and logger services on the physical machine.
+ * If the worker node is scaled down, determine the physical machine where the worker service is to be scaled down and stop the worker services on the physical machine.
```shell
# stop command:
@@ -194,7 +190,6 @@ bin/stop-all.sh # stop all services
sh bin/dolphinscheduler-daemon.sh stop master-server # stop master service
sh bin/dolphinscheduler-daemon.sh stop worker-server # stop worker service
-sh bin/dolphinscheduler-daemon.sh stop logger-server # stop logger service
sh bin/dolphinscheduler-daemon.sh stop api-server # stop api service
sh bin/dolphinscheduler-daemon.sh stop alert-server # stop alert service
@@ -204,7 +199,6 @@ bin/start-all.sh # start all services
sh bin/dolphinscheduler-daemon.sh start master-server # start master service
sh bin/dolphinscheduler-daemon.sh start worker-server # start worker service
-sh bin/dolphinscheduler-daemon.sh start logger-server # start logger service
sh bin/dolphinscheduler-daemon.sh start api-server # start api service
sh bin/dolphinscheduler-daemon.sh start alert-server # start alert service
@@ -219,7 +213,6 @@ sh bin/dolphinscheduler-daemon.sh start alert-server # start alert service
```
MasterServer ----- master service
WorkerServer ----- worker service
- LoggerServer ----- logger service
ApiApplicationServer ----- api service
AlertServer ----- alert service
```
diff --git a/docs/en-us/dev/user_doc/guide/installation/docker.md b/docs/en-us/dev/user_doc/guide/installation/docker.md
index 39af34c..53c7f1e 100644
--- a/docs/en-us/dev/user_doc/guide/installation/docker.md
+++ b/docs/en-us/dev/user_doc/guide/installation/docker.md
@@ -108,7 +108,6 @@ The following services are automatically started when the container starts:
```
MasterServer ----- master service
WorkerServer ----- worker service
- LoggerServer ----- logger service
ApiApplicationServer ----- api service
AlertServer ----- alert service
```
@@ -127,7 +126,7 @@ $ docker run -d --name dolphinscheduler-master \
apache/dolphinscheduler:1.3.8 master-server
```
-* Start a **worker server** (including **logger server**), For example:
+* Start a **worker server**, For example:
```
$ docker run -d --name dolphinscheduler-worker \
@@ -772,7 +771,7 @@ This environment variable sets zookeeper root directory for dolphinscheduler. Th
**`DOLPHINSCHEDULER_OPTS`**
-This environment variable sets JVM options for dolphinscheduler, suitable for `master-server`, `worker-server`, `api-server`, `alert-server`, `logger-server`. The default value is empty.
+This environment variable sets JVM options for dolphinscheduler, suitable for `master-server`, `worker-server`, `api-server`, `alert-server`. The default value is empty.
**`DATA_BASEDIR_PATH`**
@@ -1025,9 +1024,3 @@ This environment variable sets enterprise wechat users for `alert-server`. The d
**`API_SERVER_OPTS`**
This environment variable sets JVM options for `api-server`. The default value is `-Xms512m -Xmx512m -Xmn256m`.
-
-### Logger Server
-
-**`LOGGER_SERVER_OPTS`**
-
-This environment variable sets JVM options for `logger-server`. The default value is `-Xms512m -Xmx512m -Xmn256m`.
diff --git a/docs/en-us/dev/user_doc/guide/installation/kubernetes.md b/docs/en-us/dev/user_doc/guide/installation/kubernetes.md
index 99cd53f..434bf54 100644
--- a/docs/en-us/dev/user_doc/guide/installation/kubernetes.md
+++ b/docs/en-us/dev/user_doc/guide/installation/kubernetes.md
@@ -644,7 +644,6 @@ common:
| `worker.nodeSelector` | NodeSelector is a selector which must be true for the pod to fit on a node | `{}` |
| `worker.tolerations` | If specified, the pod's tolerations | `{}` |
| `worker.resources` | The `resource` limit and request config for worker server | `{}` |
-| `worker.configmap.LOGGER_SERVER_OPTS` | The jvm options for logger server | `-Xms512m -Xmx512m -Xmn256m` |
| `worker.configmap.WORKER_SERVER_OPTS` | The jvm options for worker server | `-Xms1g -Xmx1g -Xmn512m` |
| `worker.configmap.WORKER_EXEC_THREADS` | Worker execute thread number to limit task instances | `100` |
| `worker.configmap.WORKER_HEARTBEAT_INTERVAL` | Worker heartbeat interval, the unit is second | `10` |
diff --git a/docs/en-us/dev/user_doc/guide/installation/pseudo-cluster.md b/docs/en-us/dev/user_doc/guide/installation/pseudo-cluster.md
index d4a0ce9..aad5e2b 100644
--- a/docs/en-us/dev/user_doc/guide/installation/pseudo-cluster.md
+++ b/docs/en-us/dev/user_doc/guide/installation/pseudo-cluster.md
@@ -1,6 +1,6 @@
# Pseudo-Cluster Deployment
-The purpose of pseudo-cluster deployment is to deploy the DolphinScheduler service on a single machine. In this mode, DolphinScheduler's master, worker, api server, and logger server are all on the same machine.
+The purpose of pseudo-cluster deployment is to deploy the DolphinScheduler service on a single machine. In this mode, DolphinScheduler's master, worker, api server, are all on the same machine.
If you are a green hand and want to experience DolphinScheduler, we recommended you install follow [Standalone](standalone.md). If you want to experience more complete functions or schedule large tasks number, we recommended you install follow [pseudo-cluster deployment](pseudo-cluster.md). If you want to using DolphinScheduler in production, we recommended you follow [cluster deployment](cluster.md) or [kubernetes](kubernetes.md)
@@ -186,10 +186,6 @@ sh ./bin/dolphinscheduler-daemon.sh stop worker-server
sh ./bin/dolphinscheduler-daemon.sh start api-server
sh ./bin/dolphinscheduler-daemon.sh stop api-server
-# Start or stop Logger
-sh ./bin/dolphinscheduler-daemon.sh start logger-server
-sh ./bin/dolphinscheduler-daemon.sh stop logger-server
-
# Start or stop Alert
sh ./bin/dolphinscheduler-daemon.sh start alert-server
sh ./bin/dolphinscheduler-daemon.sh stop alert-server
diff --git a/docs/zh-cn/dev/user_doc/architecture/design.md b/docs/zh-cn/dev/user_doc/architecture/design.md
index 2cfae15..b61ceb8 100644
--- a/docs/zh-cn/dev/user_doc/architecture/design.md
+++ b/docs/zh-cn/dev/user_doc/architecture/design.md
@@ -77,8 +77,6 @@
##### 该服务包含：
- **FetchTaskThread**主要负责不断从**Task Queue**中领取任务，并根据不同任务类型调用**TaskScheduleThread**对应执行器。
- - **LoggerServer**是一个RPC服务，提供日志分片查看、刷新和下载等功能
-
* **ZooKeeper**
ZooKeeper服务，系统中的MasterServer和WorkerServer节点都通过ZooKeeper来进行集群管理和容错。另外系统还基于ZooKeeper进行事件监听和分布式锁。
diff --git a/docs/zh-cn/dev/user_doc/expansion-reduction.md b/docs/zh-cn/dev/user_doc/expansion-reduction.md
index 006a86c..60b739d 100644
--- a/docs/zh-cn/dev/user_doc/expansion-reduction.md
+++ b/docs/zh-cn/dev/user_doc/expansion-reduction.md
@@ -138,7 +138,6 @@ bin/stop-all.sh 停止所有服务
sh bin/dolphinscheduler-daemon.sh stop master-server 停止 master 服务
sh bin/dolphinscheduler-daemon.sh stop worker-server 停止 worker 服务
-sh bin/dolphinscheduler-daemon.sh stop logger-server 停止 logger 服务
sh bin/dolphinscheduler-daemon.sh stop api-server 停止 api 服务
sh bin/dolphinscheduler-daemon.sh stop alert-server 停止 alert 服务
@@ -148,7 +147,6 @@ bin/start-all.sh 启动所有服务
sh bin/dolphinscheduler-daemon.sh start master-server 启动 master 服务
sh bin/dolphinscheduler-daemon.sh start worker-server 启动 worker 服务
-sh bin/dolphinscheduler-daemon.sh start logger-server 启动 logger 服务
sh bin/dolphinscheduler-daemon.sh start api-server 启动 api 服务
sh bin/dolphinscheduler-daemon.sh start alert-server 启动 alert 服务
@@ -164,7 +162,6 @@ sh bin/dolphinscheduler-daemon.sh start alert-server 启动 alert 服务
```
MasterServer ----- master服务
WorkerServer ----- worker服务
- LoggerServer ----- logger服务
ApiApplicationServer ----- api服务
AlertServer ----- alert服务
```
@@ -175,9 +172,8 @@ sh bin/dolphinscheduler-daemon.sh start alert-server 启动 alert 服务
logs/
├── dolphinscheduler-alert-server.log
├── dolphinscheduler-master-server.log
- |—— dolphinscheduler-worker-server.log
- |—— dolphinscheduler-api-server.log
- |—— dolphinscheduler-logger-server.log
+ ├── dolphinscheduler-worker-server.log
+ ├── dolphinscheduler-api-server.log
```
如果以上服务都正常启动且调度系统页面正常,在web系统的[监控中心]查看是否有扩容的Master或者Worker服务.如果存在,则扩容完成
@@ -189,7 +185,7 @@ sh bin/dolphinscheduler-daemon.sh start alert-server 启动 alert 服务
### 2.1 停止缩容节点上的服务
* 如果缩容master节点,要确定要缩容master服务所在的物理机,并在物理机上停止该master服务.
- * 如果缩容worker节点,要确定要缩容worker服务所在的物理机,并在物理机上停止worker和logger服务.
+ * 如果缩容worker节点,要确定要缩容worker服务所在的物理机,并在物理机上停止worker服务.
```shell
停止命令:
@@ -197,7 +193,6 @@ bin/stop-all.sh 停止所有服务
sh bin/dolphinscheduler-daemon.sh stop master-server 停止 master 服务
sh bin/dolphinscheduler-daemon.sh stop worker-server 停止 worker 服务
-sh bin/dolphinscheduler-daemon.sh stop logger-server 停止 logger 服务
sh bin/dolphinscheduler-daemon.sh stop api-server 停止 api 服务
sh bin/dolphinscheduler-daemon.sh stop alert-server 停止 alert 服务
@@ -207,7 +202,6 @@ bin/start-all.sh 启动所有服务
sh bin/dolphinscheduler-daemon.sh start master-server 启动 master 服务
sh bin/dolphinscheduler-daemon.sh start worker-server 启动 worker 服务
-sh bin/dolphinscheduler-daemon.sh start logger-server 启动 logger 服务
sh bin/dolphinscheduler-daemon.sh start api-server 启动 api 服务
sh bin/dolphinscheduler-daemon.sh start alert-server 启动 alert 服务
@@ -222,7 +216,6 @@ sh bin/dolphinscheduler-daemon.sh start alert-server 启动 alert 服务
```
MasterServer ----- master服务
WorkerServer ----- worker服务
- LoggerServer ----- logger服务
ApiApplicationServer ----- api服务
AlertServer ----- alert服务
```
diff --git a/docs/zh-cn/dev/user_doc/guide/installation/docker.md b/docs/zh-cn/dev/user_doc/guide/installation/docker.md
index 6e7f9f1..a166cb4 100644
--- a/docs/zh-cn/dev/user_doc/guide/installation/docker.md
+++ b/docs/zh-cn/dev/user_doc/guide/installation/docker.md
@@ -108,7 +108,6 @@ apache/dolphinscheduler:1.3.8 all
```
MasterServer ----- master服务
WorkerServer ----- worker服务
- LoggerServer ----- logger服务
ApiApplicationServer ----- api服务
AlertServer ----- alert服务
```
@@ -127,7 +126,7 @@ $ docker run -d --name dolphinscheduler-master \
apache/dolphinscheduler:1.3.8 master-server
```
-* 启动一个 **worker server** (包括 **logger server**), 如下:
+* 启动一个 **worker server**, 如下:
```
$ docker run -d --name dolphinscheduler-worker \
@@ -772,7 +771,7 @@ SW_GRPC_LOG_SERVER_PORT=11800
**`DOLPHINSCHEDULER_OPTS`**
-配置`dolphinscheduler`的`jvm options`，适用于`master-server`、`worker-server`、`api-server`、`alert-server`、`logger-server`，默认值 `""`、
+配置`dolphinscheduler`的`jvm options`，适用于`master-server`、`worker-server`、`api-server`、`alert-server`，默认值 `""`、
**`DATA_BASEDIR_PATH`**
@@ -1025,9 +1024,3 @@ SW_GRPC_LOG_SERVER_PORT=11800
**`API_SERVER_OPTS`**
配置`api-server`的`jvm options`，默认值 `-Xms512m -Xmx512m -Xmn256m`。
-
-### Logger Server
-
-**`LOGGER_SERVER_OPTS`**
-
-配置`logger-server`的`jvm options`，默认值 `-Xms512m -Xmx512m -Xmn256m`。
diff --git a/docs/zh-cn/dev/user_doc/guide/installation/kubernetes.md b/docs/zh-cn/dev/user_doc/guide/installation/kubernetes.md
index 26ed361..bbc9fb9 100644
--- a/docs/zh-cn/dev/user_doc/guide/installation/kubernetes.md
+++ b/docs/zh-cn/dev/user_doc/guide/installation/kubernetes.md
@@ -645,7 +645,6 @@ common:
| `worker.nodeSelector` | NodeSelector is a selector which must be true for the pod to fit on a node | `{}` |
| `worker.tolerations` | If specified, the pod's tolerations | `{}` |
| `worker.resources` | The `resource` limit and request config for worker server | `{}` |
-| `worker.configmap.LOGGER_SERVER_OPTS` | The jvm options for logger server | `-Xms512m -Xmx512m -Xmn256m` |
| `worker.configmap.WORKER_SERVER_OPTS` | The jvm options for worker server | `-Xms1g -Xmx1g -Xmn512m` |
| `worker.configmap.WORKER_EXEC_THREADS` | Worker execute thread number to limit task instances | `100` |
| `worker.configmap.WORKER_HEARTBEAT_INTERVAL` | Worker heartbeat interval, the unit is second | `10` |
diff --git a/docs/zh-cn/dev/user_doc/guide/installation/pseudo-cluster.md b/docs/zh-cn/dev/user_doc/guide/installation/pseudo-cluster.md
index 3eccc0e..baae00d 100644
--- a/docs/zh-cn/dev/user_doc/guide/installation/pseudo-cluster.md
+++ b/docs/zh-cn/dev/user_doc/guide/installation/pseudo-cluster.md
@@ -1,6 +1,6 @@
# 伪集群部署
-伪集群部署目的是在单台机器部署 DolphinScheduler 服务，该模式下master、worker、api server、logger server都在同一台机器上
+伪集群部署目的是在单台机器部署 DolphinScheduler 服务，该模式下master、worker、api server 都在同一台机器上
如果你是新手，想要体验 DolphinScheduler 的功能，推荐使用[Standalone](standalone.md)方式体检。如果你想体验更完整的功能，或者更大的任务量，推荐使用[伪集群部署](pseudo-cluster.md)。如果你是在生产中使用，推荐使用[集群部署](cluster.md)或者[kubernetes](kubernetes.md)
@@ -185,10 +185,6 @@ sh ./bin/dolphinscheduler-daemon.sh stop worker-server
sh ./bin/dolphinscheduler-daemon.sh start api-server
sh ./bin/dolphinscheduler-daemon.sh stop api-server
-# 启停 Logger
-sh ./bin/dolphinscheduler-daemon.sh start logger-server
-sh ./bin/dolphinscheduler-daemon.sh stop logger-server
-
# 启停 Alert
sh ./bin/dolphinscheduler-daemon.sh start alert-server
sh ./bin/dolphinscheduler-daemon.sh stop alert-server