|
@@ -11,7 +11,7 @@ DolphinScheduler, as an open-source distributed workflow task scheduling system,
|
|
|
| Oracle Enterprise Linux | 7.0 and above |
|
|
|
| Ubuntu LTS | 16.04 and above |
|
|
|
|
|
|
-> **Attention:**
|
|
|
+> **Note:**
|
|
|
>The above Linux operating systems can run on physical servers and mainstream virtualization environments such as VMware, KVM, and XEN.
|
|
|
|
|
|
## Recommended Server Configuration
|
|
@@ -24,7 +24,7 @@ DolphinScheduler supports 64-bit hardware platforms with Intel x86-64 architectu
|
|
|
| --- | --- | --- | --- | --- |
|
|
|
| 4 core+ | 8 GB+ | SAS | GbE | 1+ |
|
|
|
|
|
|
-> **Attention:**
|
|
|
+> **Note:**
|
|
|
> - The above recommended configuration is the minimum configuration for deploying DolphinScheduler. Higher configuration is strongly recommended for production environments.
|
|
|
> - The recommended hard disk size is more than 50GB and separate the system disk and data disk.
|
|
|
|
|
@@ -39,7 +39,7 @@ DolphinScheduler provides the following network port configurations for normal o
|
|
|
| WorkerServer | 1234 | not the communication port, require the native ports do not conflict |
|
|
|
| ApiApplicationServer | 12345 | backend communication port |
|
|
|
|
|
|
-> **Attention:**
|
|
|
+> **Note:**
|
|
|
> - MasterServer and WorkerServer do not need to enable communication between the networks. As long as the local ports do not conflict.
|
|
|
> - Administrators can adjust relevant ports on the network side and host-side according to the deployment plan of DolphinScheduler components in the actual environment.
|
|
|
|