@ -6,7 +6,7 @@ This article describes how to add a new master service or worker service to an e
```
```
Attention: There cannot be more than one master service process or worker service process on a physical machine.
Attention: There cannot be more than one master service process or worker service process on a physical machine.
If the physical machine which locate the expansion master or worker node has already installed the scheduled service, check the [1.4 Modify configuration] and edit the configuration file `conf/config/install_config.conf` on ** all ** nodes, add masters or workers parameter, and restart the scheduling cluster.
If the physical machine which locate the expansion master or worker node has already installed the scheduled service, check the [1.4 Modify configuration] and edit the configuration file `bin/env/install_env.sh` on ** all ** nodes, add masters or workers parameter, and restart the scheduling cluster.
```
```
### Basic software installation
### Basic software installation
@ -96,7 +96,7 @@ Attention:
```shell
```shell
sudo ln -s /opt/soft/java/bin/java /usr/bin/java
sudo ln -s /opt/soft/java/bin/java /usr/bin/java
```
```
- Modify the configuration file `conf/config/install_config.conf` on the **all** nodes, synchronizing the following configuration.
- Modify the configuration file `bin/env/install_env.sh` on the **all** nodes, synchronizing the following configuration.
* To add a new master node, you need to modify the IPs and masters parameters.
* To add a new master node, you need to modify the IPs and masters parameters.
* To add a new worker node, modify the IPs and workers parameters.
* To add a new worker node, modify the IPs and workers parameters.
@ -222,7 +222,7 @@ If the corresponding master service or worker service does not exist, then the m
### Modify the Configuration File
### Modify the Configuration File
- modify the configuration file `conf/config/install_config.conf` on the **all** nodes, synchronizing the following configuration.
- modify the configuration file `bin/env/install_env.sh` on the **all** nodes, synchronizing the following configuration.
* to scale down the master node, modify the IPs and masters parameters.
* to scale down the master node, modify the IPs and masters parameters.
* to scale down worker nodes, modify the IPs and workers parameters.
* to scale down worker nodes, modify the IPs and workers parameters.
- If you deploy with Pseudo-Cluster deployment, change it according to [Pseudo-Cluster](../installation/pseudo-cluster.md) section "Modify Configuration".
- If you deploy with Pseudo-Cluster deployment, change it according to [Pseudo-Cluster](../installation/pseudo-cluster.md) section "Modify Configuration".
- If you deploy with Cluster deployment, change it according to [Cluster](../installation/cluster.md) section "Modify Configuration".
- If you deploy with Cluster deployment, change it according to [Cluster](../installation/cluster.md) section "Modify Configuration".
@ -65,7 +65,7 @@ The architecture of worker group is different between version before version 1.3
| 1 | service1 | 192.168.xx.10 |
| 1 | service1 | 192.168.xx.10 |
| 2 | service2 | 192.168.xx.11,192.168.xx.12 |
| 2 | service2 | 192.168.xx.11,192.168.xx.12 |
- Modify worker related configuration in `bin/env/install_config.conf`.
- Modify worker related configuration in `bin/env/install_env.sh`.
Assume below are the machine worker service to be deployed:
Assume below are the machine worker service to be deployed: