[Fix][Doc] Replace the links. (#13276)
* [Fix][Doc] Replace the links. * [Fix][Doc] Revised `.dlc.json` * [Fix] Fix the dead link.
This commit is contained in:
parent
a75a69f3ec
commit
1f7f900e78
13
.dlc.json
13
.dlc.json
|
|
@ -8,16 +8,19 @@
|
|||
},
|
||||
{
|
||||
"pattern": "/community/community.html$"
|
||||
},
|
||||
{
|
||||
"pattern": "^https://dolphinscheduler.apache.org"
|
||||
}
|
||||
],
|
||||
"replacementPatterns": [
|
||||
{
|
||||
"pattern": "^/en-us/download/download.html$",
|
||||
"replacement": "https://dolphinscheduler.apache.org/en-us/download/download.html"
|
||||
"replacement": "https://dolphinscheduler.apache.org/en-us/download"
|
||||
},
|
||||
{
|
||||
"pattern": "^/zh-cn/download/download.html$",
|
||||
"replacement": "https://dolphinscheduler.apache.org/zh-cn/download/download.html"
|
||||
"replacement": "https://dolphinscheduler.apache.org/zh-cn/download"
|
||||
}
|
||||
],
|
||||
"httpHeaders": [
|
||||
|
|
@ -32,9 +35,5 @@
|
|||
"retryOn429": true,
|
||||
"retryCount": 10,
|
||||
"fallbackRetryDelay": "1000s",
|
||||
"aliveStatusCodes": [
|
||||
200,
|
||||
401,
|
||||
0
|
||||
]
|
||||
"aliveStatusCodes": [200, 401, 0]
|
||||
}
|
||||
|
|
|
|||
|
|
@ -54,11 +54,11 @@ The key features for DolphinScheduler are as follows:
|
|||
|
||||
## QuickStart in Docker
|
||||
|
||||
Please refer the official website document: [QuickStart in Docker](https://dolphinscheduler.apache.org/#/en-us/docs/3.1.2/guide/start/docker)
|
||||
Please refer the official website document: [QuickStart in Docker](https://dolphinscheduler.apache.org/en-us/docs/3.1.2/guide/start/docker)
|
||||
|
||||
## QuickStart in Kubernetes
|
||||
|
||||
Please refer to the official website document: [QuickStart in Kubernetes](https://dolphinscheduler.apache.org/#/en-us/docs/3.1.2/guide/installation/kubernetes)
|
||||
Please refer to the official website document: [QuickStart in Kubernetes](https://dolphinscheduler.apache.org/en-us/docs/3.1.2/guide/installation/kubernetes)
|
||||
|
||||
## How to Build
|
||||
|
||||
|
|
|
|||
|
|
@ -51,11 +51,11 @@ DolphinScheduler 的工作计划:<a href="https://github.com/apache/dolphinsch
|
|||
|
||||
## 快速试用 Docker
|
||||
|
||||
请参考官方文档: [快速试用 Docker 部署](https://dolphinscheduler.apache.org/#/zh-cn/docs/3.1.2/guide/start/docker)
|
||||
请参考官方文档: [快速试用 Docker 部署](https://dolphinscheduler.apache.org/zh-cn/docs/3.1.2/guide/start/docker)
|
||||
|
||||
## 快速试用 Kubernetes
|
||||
|
||||
请参考官方文档: [快速试用 Kubernetes 部署](http://dolphinscheduler.apache.org/#/zh-cn/docs/3.1.2/guide/installation/kubernetes)
|
||||
请参考官方文档: [快速试用 Kubernetes 部署](https://dolphinscheduler.apache.org/zh-cn/docs/3.1.2/guide/installation/kubernetes)
|
||||
|
||||
## 如何构建
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# DolphinScheduler for Docker and Kubernetes
|
||||
|
||||
- [Start Up DolphinScheduler with Docker](https://dolphinscheduler.apache.org/#/en-us/docs/3.1.2/guide/start/docker)
|
||||
- [Start Up DolphinScheduler with Kubernetes](https://dolphinscheduler.apache.org/#/en-us/docs/3.1.2/guide/installation/kubernetes)
|
||||
- [Start Up DolphinScheduler with Docker](https://dolphinscheduler.apache.org/en-us/docs/3.1.2/guide/start/docker)
|
||||
- [Start Up DolphinScheduler with Kubernetes](https://dolphinscheduler.apache.org/en-us/docs/3.1.2/guide/installation/kubernetes)
|
||||
|
|
|
|||
|
|
@ -90,7 +90,7 @@ Before explaining the architecture of the schedule system, let us first understa
|
|||
|
||||
- **UI**
|
||||
|
||||
The front-end page of the system provides various visual operation interfaces of the system. For details, see the [quick start](https://dolphinscheduler.apache.org/#/en-us/docs/3.1.2/about/introduction) section.
|
||||
The front-end page of the system provides various visual operation interfaces of the system. For details, see the [quick start](https://dolphinscheduler.apache.org/en-us/docs/3.1.2/about/introduction) section.
|
||||
|
||||
#### 2.3 Architectural Design Ideas
|
||||
|
||||
|
|
|
|||
|
|
@ -120,7 +120,7 @@ There are two ways to configure the DolphinScheduler development environment, st
|
|||
>
|
||||
> Standalone is only supported in DolphinScheduler 1.3.9 and later versions.
|
||||
>
|
||||
> Standalone server is able to connect to external databases like mysql and postgresql, see [Standalone Deployment](https://dolphinscheduler.apache.org/#/en-us/docs/3.1.2/guide/installation/standalone) for instructions.
|
||||
> Standalone server is able to connect to external databases like mysql and postgresql, see [Standalone Deployment](https://dolphinscheduler.apache.org/en-us/docs/3.1.2/guide/installation/standalone) for instructions.
|
||||
|
||||
### Git Branch Choose
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Community Review
|
||||
|
||||
Beside submit Issues and pull requests to the GitHub repository mentioned in [team](https://dolphinscheduler.apache.org/#/en-us/community), another important way to
|
||||
Beside submit Issues and pull requests to the GitHub repository mentioned in [team](https://dolphinscheduler.apache.org/en-us/community), another important way to
|
||||
contribute to DolphinScheduler is reviewing GitHub Issues or Pull Requests. You can not only know the latest new and
|
||||
direction of the community, but also understand the good design in others during you reviewing. At the same time, you can
|
||||
increase your exposure in the community and accumulate your honor.
|
||||
|
|
@ -12,7 +12,7 @@ in [GitHub Discussion][discussion-result-review-wanted].
|
|||
> Note: It is only users mentioned in the [GitHub Discussion][discussion-result-review-wanted] can review Issues or Pull
|
||||
> Requests, Community advocates **Anyone is encouraged to review Issues and Pull Requests**. Users in
|
||||
> [GitHub Discussion][discussion-result-review-wanted] show their willing to review when we collect in the mail thread.
|
||||
> The advantage of this list is when the community has discussion, in addition to the mention Members in [team](https://dolphinscheduler.apache.org/#/en-us/community),
|
||||
> The advantage of this list is when the community has discussion, in addition to the mention Members in [team](https://dolphinscheduler.apache.org/en-us/community),
|
||||
> you can also find some help in [GitHub Discussion][discussion-result-review-wanted] people. If you want to join the
|
||||
> [GitHub Discussion][discussion-result-review-wanted], please comment in that discussion and leave a module you are interested
|
||||
> in, and the maintainer will add you to the list.
|
||||
|
|
|
|||
|
|
@ -564,7 +564,7 @@ Dolphin Scheduler is a distributed and easy-to-extend visual workflow scheduler
|
|||
dedicated to solving the complex task dependencies in data processing, making the scheduler system out of the box for data processing.
|
||||
|
||||
|
||||
Download Links: https://dolphinscheduler.apache.org/#/en-us/download
|
||||
Download Links: https://dolphinscheduler.apache.org/en-us/download
|
||||
|
||||
Release Notes: https://github.com/apache/dolphinscheduler/releases/tag/<VERSION>
|
||||
|
||||
|
|
@ -573,7 +573,7 @@ Website: https://dolphinscheduler.apache.org/
|
|||
DolphinScheduler Resources:
|
||||
- Issue: https://github.com/apache/dolphinscheduler/issues/
|
||||
- Mailing list: dev@dolphinscheduler.apache.org
|
||||
- Documents: https://dolphinscheduler.apache.org/#/zh-cn/docs/<VERSION>/about/introduction
|
||||
- Documents: https://dolphinscheduler.apache.org/zh-cn/docs/<VERSION>/about/introduction
|
||||
```
|
||||
|
||||
## News
|
||||
|
|
|
|||
|
|
@ -298,9 +298,9 @@ change into
|
|||
|
||||
## Q : how to add a worker server
|
||||
|
||||
A: 1, Create deployment user and hosts mapping, please refer 1.3 part of [cluster deployment](https://dolphinscheduler.apache.org/#/en-us/docs/3.1.2/user_doc/installation/cluster)
|
||||
A: 1, Create deployment user and hosts mapping, please refer 1.3 part of [cluster deployment](https://dolphinscheduler.apache.org/en-us/docs/3.1.2/user_doc/installation/cluster)
|
||||
|
||||
2, Configure hosts mapping and ssh access and modify directory permissions. please refer 1.4 part of [cluster deployment](https://dolphinscheduler.apache.org/#/en-us/docs/3.1.2/user_doc/installation/cluster)
|
||||
2, Configure hosts mapping and ssh access and modify directory permissions. please refer 1.4 part of [cluster deployment](https://dolphinscheduler.apache.org/en-us/docs/3.1.2/user_doc/installation/cluster)
|
||||
|
||||
3, Copy the deployment directory from worker server that has already deployed
|
||||
|
||||
|
|
@ -762,6 +762,7 @@ A: For the task identified as `Cache Execution`, when the task starts, a cache k
|
|||
- environment configuration: the actual configuration content of the environment configuration under the environment name, that is, the actual configuration content in the `security` - `environment management`
|
||||
|
||||
If the task with cache identification runs, it will find whether there is data with the same cache key in the database,
|
||||
|
||||
- If there is, copy the task instance and update the corresponding data
|
||||
- If not, the task runs as usual, and the task instance data is stored in the cache when the task is completed
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ To prevent data loss by some miss-operation, it is recommended to back up data b
|
|||
|
||||
### Download the Latest Version Installation Package
|
||||
|
||||
Download the latest binary distribute package from [download](https://dolphinscheduler.apache.org/#/en-us/download) and then put it in the different
|
||||
Download the latest binary distribute package from [download](https://dolphinscheduler.apache.org/en-us/download) and then put it in the different
|
||||
directory where current service running. And all below command is running in this directory.
|
||||
|
||||
## Start
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ If you are a new hand and want to experience DolphinScheduler functions, we reco
|
|||
|
||||
## Install DolphinScheduler
|
||||
|
||||
Please download the source code package `apache-dolphinscheduler-<version>-src.tar.gz`, download address: [download address](https://dolphinscheduler.apache.org/#/en-us/download)
|
||||
Please download the source code package `apache-dolphinscheduler-<version>-src.tar.gz`, download address: [download address](https://dolphinscheduler.apache.org/en-us/download)
|
||||
|
||||
To publish the release name `dolphinscheduler` version, please execute the following commands:
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ If you are a new hand and want to experience DolphinScheduler functions, we reco
|
|||
Pseudo-cluster deployment of DolphinScheduler requires external software support:
|
||||
|
||||
- JDK:download [JDK][jdk] (1.8+), install and configure environment variable `JAVA_HOME` and append `bin` dir (included in `JAVA_HOME`) to `PATH` variable. You can skip this step if it already exists in your environment.
|
||||
- Binary package: Download the DolphinScheduler binary package at [download page](https://dolphinscheduler.apache.org/#/en-us/download)
|
||||
- Binary package: Download the DolphinScheduler binary package at [download page](https://dolphinscheduler.apache.org/en-us/download)
|
||||
- Database: [PostgreSQL](https://www.postgresql.org/download/) (8.2.15+) or [MySQL](https://dev.mysql.com/downloads/mysql/) (5.7+), you can choose one of the two, such as MySQL requires JDBC Driver 8.0.16
|
||||
- Registry Center: [ZooKeeper](https://zookeeper.apache.org/releases.html) (3.8.0+),[download link][zookeeper]
|
||||
- Process tree analysis
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ If you want to deploy DolphinScheduler in production, we recommend you follow [c
|
|||
## Preparation
|
||||
|
||||
- JDK:download [JDK][jdk] (1.8+), install and configure environment variable `JAVA_HOME` and append `bin` dir (included in `JAVA_HOME`) to `PATH` variable. You can skip this step if it already exists in your environment.
|
||||
- Binary package: download the DolphinScheduler binary package at [download page](https://dolphinscheduler.apache.org/#/en-us/download).
|
||||
- Binary package: download the DolphinScheduler binary package at [download page](https://dolphinscheduler.apache.org/en-us/download).
|
||||
|
||||
## Start DolphinScheduler Standalone Server
|
||||
|
||||
|
|
|
|||
|
|
@ -45,7 +45,7 @@ modify docker-compose's free memory up to 4 GB.
|
|||
- Hyper-V mode: Click `Docker Desktop -> Settings -> Resources -> Memory` modified it
|
||||
- WSL 2 mode: see [WSL 2 utility VM](https://docs.microsoft.com/zh-cn/windows/wsl/wsl-config#configure-global-options-with-wslconfig) for more detail.
|
||||
|
||||
After complete the configuration, we can get the `docker-compose.yaml` file from [download page](https://dolphinscheduler.apache.org/#/en-us/download)
|
||||
After complete the configuration, we can get the `docker-compose.yaml` file from [download page](https://dolphinscheduler.apache.org/en-us/download)
|
||||
form its source package, and make sure you get the right version. After download the package, you can run the commands as below.
|
||||
|
||||
```shell
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ To prevent data loss by some miss-operation, it is recommended to back up data b
|
|||
|
||||
### Download the Latest Version Installation Package
|
||||
|
||||
Download the latest binary distribute package from [download](https://dolphinscheduler.apache.org/#/en-us/download) and then put it in the different
|
||||
Download the latest binary distribute package from [download](https://dolphinscheduler.apache.org/en-us/download) and then put it in the different
|
||||
directory where current service running. And all below command is running in this directory.
|
||||
|
||||
## Upgrade
|
||||
|
|
|
|||
|
|
@ -90,7 +90,7 @@
|
|||
|
||||
- **UI**
|
||||
|
||||
系统的前端页面,提供系统的各种可视化操作界面,详见 [快速开始](https://dolphinscheduler.apache.org/#/zh-cn/docs/3.1.2/about/introduction) 部分。
|
||||
系统的前端页面,提供系统的各种可视化操作界面,详见 [快速开始](https://dolphinscheduler.apache.org/zh-cn/docs/3.1.2/about/introduction) 部分。
|
||||
|
||||
#### 2.3 架构设计思想
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# 参与社区 review
|
||||
|
||||
贡献 DolphinScheduler 的方式,除了向 [团队](https://dolphinscheduler.apache.org/#/zh-cn/community) 中提到的 GitHub 仓库提交 Issues 和 pull requests 外,另一非常重要的方式是
|
||||
贡献 DolphinScheduler 的方式,除了向 [团队](https://dolphinscheduler.apache.org/zh-cn/community) 中提到的 GitHub 仓库提交 Issues 和 pull requests 外,另一非常重要的方式是
|
||||
review 社区的 Issues 或者 Pull Requests。通过别人 Issues 和 Pull Requests,你不仅能知道社区的最新进展和发展方向,还能了解别人代码的设
|
||||
计思想,同时可以增加自己在社区的曝光、积累自己在社区的荣誉值。
|
||||
|
||||
|
|
@ -9,7 +9,7 @@ review 社区的 Issues 或者 Pull Requests。通过别人 Issues 和 Pull Requ
|
|||
|
||||
> 注意: 这里并不是说只有 [GitHub Discussion][discussion-result-review-wanted] 中提及的用户才可以协助 review Issue 或者 Pull Requests,
|
||||
> 请记住社区的主张是 **任何人都被鼓励去 review 社区的 Issues 和 Pull Requests**。只是那部分用户在邮件列表意见征集的时候,表达了愿意付
|
||||
> 出更多的时间,参与社区的 review。另一个好处是,当社区有不确定的问题的时,除了可以找 [团队](https://dolphinscheduler.apache.org/#/zh-cn/community) 中对应的 Members 外,还可以找
|
||||
> 出更多的时间,参与社区的 review。另一个好处是,当社区有不确定的问题的时,除了可以找 [团队](https://dolphinscheduler.apache.org/zh-cn/community) 中对应的 Members 外,还可以找
|
||||
> [GitHub Discussion][discussion-result-review-wanted] 中提及的人解答对应的问题。如果你要想要加入到 [GitHub Discussion][discussion-result-review-wanted]
|
||||
> 中,请在该 discussion 中评论并留下你感兴趣的模块,维护者会将你加入到对应的名单中。
|
||||
|
||||
|
|
|
|||
|
|
@ -415,7 +415,7 @@ Release Commit ID: https://github.com/apache/dolphinscheduler/commit/<SHA-VALUE>
|
|||
|
||||
Keys to verify the Release Candidate: https://downloads.apache.org/dolphinscheduler/KEYS
|
||||
|
||||
Look at here for how to verify this release candidate: https://dolphinscheduler.apache.org/#/zh-cn/docs/3.1.2/contribute/release/release
|
||||
Look at here for how to verify this release candidate: https://dolphinscheduler.apache.org/zh-cn/docs/3.1.2/contribute/release/release
|
||||
|
||||
The vote will be open for at least 72 hours or until necessary number of votes are reached.
|
||||
|
||||
|
|
@ -564,7 +564,7 @@ Dolphin Scheduler is a distributed and easy-to-extend visual workflow scheduler
|
|||
dedicated to solving the complex task dependencies in data processing, making the scheduler system out of the box for data processing.
|
||||
|
||||
|
||||
Download Links: https://dolphinscheduler.apache.org/#/zh-cn/download
|
||||
Download Links: https://dolphinscheduler.apache.org/zh-cn/download
|
||||
|
||||
Release Notes: https://github.com/apache/dolphinscheduler/releases/tag/<VERSION>
|
||||
|
||||
|
|
@ -573,7 +573,7 @@ Website: https://dolphinscheduler.apache.org/
|
|||
DolphinScheduler Resources:
|
||||
- Issue: https://github.com/apache/dolphinscheduler/issues/
|
||||
- Mailing list: dev@dolphinscheduler.apache.org
|
||||
- Documents: https://dolphinscheduler.apache.org/#/zh-cn/docs/<VERSION>/about/introduction
|
||||
- Documents: https://dolphinscheduler.apache.org/zh-cn/docs/<VERSION>/about/introduction
|
||||
```
|
||||
|
||||
## News
|
||||
|
|
|
|||
|
|
@ -269,9 +269,9 @@ A: 将 hive pom
|
|||
|
||||
## Q:如何增加一台工作服务器
|
||||
|
||||
A: 1,参考官网[部署文档](https://dolphinscheduler.apache.org/#/zh-cn/docs/3.1.2/installation/cluster) 1.3 小节,创建部署用户和 hosts 映射
|
||||
A: 1,参考官网[部署文档](https://dolphinscheduler.apache.org/zh-cn/docs/3.1.2/installation/cluster) 1.3 小节,创建部署用户和 hosts 映射
|
||||
|
||||
2,参考官网[部署文档](https://dolphinscheduler.apache.org/#/zh-cn/docs/3.1.2/installation/cluster) 1.4 小节,配置 hosts 映射和 ssh 打通及修改目录权限.
|
||||
2,参考官网[部署文档](https://dolphinscheduler.apache.org/zh-cn/docs/3.1.2/installation/cluster) 1.4 小节,配置 hosts 映射和 ssh 打通及修改目录权限.
|
||||
1.4 小节的最后一步是在当前新增机器上执行的,即需要给部署目录部署用户的权限
|
||||
|
||||
3,复制正在运行的服务器上的部署目录到新机器的同样的部署目录下
|
||||
|
|
@ -722,14 +722,15 @@ A:在 3.0.0-alpha 版本之后,Python gateway server 集成到 api server
|
|||
|
||||
## Q: 缓存执行时怎么判断任务已经存在缓存过的任务,即如何判断一个任务可以使用另外一个任务的运行结果?
|
||||
|
||||
A: 对于标识为`缓存执行`的任务, 当任务启动时会生成一个缓存key, 该key由以下字段组合哈希得到:
|
||||
A: 对于标识为`缓存执行`的任务, 当任务启动时会生成一个缓存 key, 该 key 由以下字段组合哈希得到:
|
||||
|
||||
- 任务定义:任务实例对应的任务定义的id
|
||||
- 任务定义:任务实例对应的任务定义的 id
|
||||
- 任务的版本:任务实例对应的任务定义的版本
|
||||
- 任务输入的参数:包括上游节点和全局参数传入的参数中,被任务定义的参数列表所引用和任务定义中使用`${}`引用的参数
|
||||
- 环境配置: 环境名称下具体的环境配置内容,具体为安全中心环境管理中的实际配置内容
|
||||
|
||||
当缓存标识的任务运行时,会查找数据库中是否用相同缓存key的数据,
|
||||
当缓存标识的任务运行时,会查找数据库中是否用相同缓存 key 的数据,
|
||||
|
||||
- 若有则复制该任务实例并进行相应数据的更新
|
||||
- 若无,则任务照常运行,并在任务完成时将任务实例的数据存入缓存
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@
|
|||
|
||||
### 下载新版本的安装包
|
||||
|
||||
在[下载](https://dolphinscheduler.apache.org/#/zh-cn/download)页面下载最新版本的二进制安装包,并将二进制包放到与当前 dolphinscheduler 服务不一样的路径中,以下服务启动操作都需要在新版本的目录进行。
|
||||
在[下载](https://dolphinscheduler.apache.org/zh-cn/download)页面下载最新版本的二进制安装包,并将二进制包放到与当前 dolphinscheduler 服务不一样的路径中,以下服务启动操作都需要在新版本的目录进行。
|
||||
|
||||
## 服务启动步骤
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ Kubernetes 部署目的是在 Kubernetes 集群中部署 DolphinScheduler 服务
|
|||
|
||||
## 安装 dolphinscheduler
|
||||
|
||||
请下载源码包 apache-dolphinscheduler-<version>-src.tar.gz,下载地址: [下载](https://dolphinscheduler.apache.org/#/zh-cn/download)
|
||||
请下载源码包 apache-dolphinscheduler-<version>-src.tar.gz,下载地址: [下载](https://dolphinscheduler.apache.org/zh-cn/download)
|
||||
|
||||
发布一个名为 `dolphinscheduler` 的版本(release),请执行以下命令:
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@
|
|||
伪分布式部署 DolphinScheduler 需要有外部软件的支持
|
||||
|
||||
- JDK:下载[JDK][jdk] (1.8+),安装并配置 `JAVA_HOME` 环境变量,并将其下的 `bin` 目录追加到 `PATH` 环境变量中。如果你的环境中已存在,可以跳过这步。
|
||||
- 二进制包:在[下载页面](https://dolphinscheduler.apache.org/#/zh-cn/download)下载 DolphinScheduler 二进制包
|
||||
- 二进制包:在[下载页面](https://dolphinscheduler.apache.org/zh-cn/download)下载 DolphinScheduler 二进制包
|
||||
- 数据库:[PostgreSQL](https://www.postgresql.org/download/) (8.2.15+) 或者 [MySQL](https://dev.mysql.com/downloads/mysql/) (5.7+),两者任选其一即可,如 MySQL 则需要 JDBC Driver 8.0.16
|
||||
- 注册中心:[ZooKeeper](https://zookeeper.apache.org/releases.html) (3.8.0+),[下载地址][zookeeper]
|
||||
- 进程树分析
|
||||
|
|
@ -138,7 +138,7 @@ export PATH=$HADOOP_HOME/bin:$SPARK_HOME/bin:$PYTHON_HOME/bin:$JAVA_HOME/bin:$HI
|
|||
|
||||
## 初始化数据库
|
||||
|
||||
请参考 [数据源配置] `伪分布式/分布式安装初始化数据库` 创建并初始化数据库
|
||||
请参考 [数据源配置] `伪分布式/分布式安装初始化数据库` 创建并初始化数据库
|
||||
|
||||
## 启动 DolphinScheduler
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ Standalone 仅适用于 DolphinScheduler 的快速体验.
|
|||
## 前置准备工作
|
||||
|
||||
- JDK:下载[JDK][jdk] (1.8+),安装并配置 `JAVA_HOME` 环境变量,并将其下的 `bin` 目录追加到 `PATH` 环境变量中。如果你的环境中已存在,可以跳过这步。
|
||||
- 二进制包:在[下载页面](https://dolphinscheduler.apache.org/#/zh-cn/download)下载 DolphinScheduler 二进制包
|
||||
- 二进制包:在[下载页面](https://dolphinscheduler.apache.org/zh-cn/download)下载 DolphinScheduler 二进制包
|
||||
|
||||
## 启动 DolphinScheduler Standalone Server
|
||||
|
||||
|
|
|
|||
|
|
@ -39,7 +39,7 @@ $ docker run --name dolphinscheduler-standalone-server -p 12345:12345 -p 25333:2
|
|||
- Hyper-V 模式:点击 `Docker Desktop -> Settings -> Resources -> Memory` 调整内存大小
|
||||
- WSL 2 模式 模式:参考 [WSL 2 utility VM](https://docs.microsoft.com/zh-cn/windows/wsl/wsl-config#configure-global-options-with-wslconfig) 调整内存大小
|
||||
|
||||
配置完成后我们需要获取 `docker-compose.yaml` 文件,通过[下载页面](https://dolphinscheduler.apache.org/#/zh-cn/download)下载对应版本源码包可能是最快的方法,
|
||||
配置完成后我们需要获取 `docker-compose.yaml` 文件,通过[下载页面](https://dolphinscheduler.apache.org/zh-cn/download)下载对应版本源码包可能是最快的方法,
|
||||
源码包对应的值为 "Total Source Code"。当下载完源码后就可以运行命令进行部署了。
|
||||
|
||||
```shell
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@
|
|||
|
||||
### 下载新版本的安装包
|
||||
|
||||
在[下载](https://dolphinscheduler.apache.org/#/zh-cn/download)页面下载最新版本的二进制安装包,并将二进制包放到与当前 dolphinscheduler 服务不一样的路径中,以下升级操作都需要在新版本的目录进行。
|
||||
在[下载](https://dolphinscheduler.apache.org/zh-cn/download)页面下载最新版本的二进制安装包,并将二进制包放到与当前 dolphinscheduler 服务不一样的路径中,以下升级操作都需要在新版本的目录进行。
|
||||
|
||||
## 升级步骤
|
||||
|
||||
|
|
|
|||
|
|
@ -33,4 +33,4 @@ After do this two steps, you can start your DolphinScheduler cluster, your clust
|
|||
store server metadata.
|
||||
|
||||
NOTE: You need to add `mysql-connector-java.jar` into DS classpath, since this plugin will not bundle this driver in distribution.
|
||||
You can get the detail about <a href="https://dolphinscheduler.apache.org/#/en-us/docs/3.1.2/guide/installation/pseudo-cluster">Initialize the Database</a>
|
||||
You can get the detail about <a href="https://dolphinscheduler.apache.org/en-us/docs/3.1.2/guide/installation/pseudo-cluster">Initialize the Database</a>
|
||||
|
|
|
|||
Loading…
Reference in New Issue