|
|
@@ -42,20 +42,13 @@ escheduler ALL=(ALL) NOPASSWD: NOPASSWD: ALL
|
|
|
#### Preparations 3: SSH Secret-Free Configuration
|
|
|
Configure SSH secret-free login on deployment machines and other installation machines. If you want to install easyscheduler on deployment machines, you need to configure native password-free login itself.
|
|
|
|
|
|
-
|
|
|
-
|
|
|
- [Connect the host and other machines SSH](http://geek.analysys.cn/topic/113)
|
|
|
|
|
|
-
|
|
|
#### Preparations 4: database initialization
|
|
|
|
|
|
* Create databases and accounts
|
|
|
|
|
|
- Enter the mysql command line service by following MySQL commands:
|
|
|
-
|
|
|
- > mysql -h {host} -u {user} -p{password}
|
|
|
-
|
|
|
- Then execute the following command to create database and account
|
|
|
+ Execute the following command to create database and account
|
|
|
|
|
|
```sql
|
|
|
CREATE DATABASE escheduler DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_general_ci;
|
|
|
@@ -64,17 +57,8 @@ Configure SSH secret-free login on deployment machines and other installation ma
|
|
|
flush privileges;
|
|
|
```
|
|
|
|
|
|
-* Versions 1.0.0 and 1.0.1 create tables and import basic data
|
|
|
- Instructions：在escheduler-backend/sql/escheduler.sql和quartz.sql
|
|
|
-
|
|
|
- ```sql
|
|
|
- mysql -h {host} -u {user} -p{password} -D {db} < escheduler.sql
|
|
|
-
|
|
|
- mysql -h {host} -u {user} -p{password} -D {db} < quartz.sql
|
|
|
- ```
|
|
|
-
|
|
|
-* Version 1.0.2 later (including 1.0.2) creates tables and imports basic data
|
|
|
- Modify the following attributes in conf/dao/data_source.properties
|
|
|
+* creates tables and imports basic data
|
|
|
+ Modify the following attributes in ./conf/dao/data_source.properties
|
|
|
|
|
|
```
|
|
|
spring.datasource.url
|
|
|
@@ -88,7 +72,7 @@ Configure SSH secret-free login on deployment machines and other installation ma
|
|
|
|
|
|
#### Preparations 5: Modify the deployment directory permissions and operation parameters
|
|
|
|
|
|
-Let's first get a general idea of the role of files (folders) in the escheduler-backend directory after decompression.
|
|
|
+ instruction of escheduler-backend directory
|
|
|
|
|
|
```directory
|
|
|
bin : Basic service startup script
|
|
|
@@ -99,7 +83,7 @@ sql : The project relies on SQL files
|
|
|
install.sh : One-click deployment script
|
|
|
```
|
|
|
|
|
|
-- Modify permissions (please modify the deployUser to the corresponding deployment user) so that the deployment user has operational privileges on the escheduler-backend directory
|
|
|
+- Modify permissions (please modify the 'deployUser' to the corresponding deployment user) so that the deployment user has operational privileges on the escheduler-backend directory
|
|
|
|
|
|
`sudo chown -R deployUser:deployUser escheduler-backend`
|
|
|
|
|
|
@@ -109,9 +93,9 @@ install.sh : One-click deployment script
|
|
|
|
|
|
- Modify the parameters in **install.sh** to replace the values required by your business
|
|
|
- MonitorServerState switch variable, added in version 1.0.3, controls whether to start the self-start script (monitor master, worker status, if off-line will start automatically). The default value of "false" means that the self-start script is not started, and if it needs to start, it is changed to "true".
|
|
|
- - hdfsStartupSate switch variable controls whether to starthdfs
|
|
|
+ - 'hdfsStartupSate' switch variable controls whether to start hdfs
|
|
|
The default value of "false" means not to start hdfs
|
|
|
- If you need to start hdfs instead of "true", you need to create the hdfs root path by yourself, that is, hdfsPath in install.sh.
|
|
|
+ Change the variable to 'true' if you want to use hdfs, you also need to create the hdfs root path by yourself, that 'hdfsPath' in install.sh.
|
|
|
|
|
|
- If you use hdfs-related functions, you need to copy**hdfs-site.xml** and **core-site.xml** to the conf directory
|
|
|
|
|
|
@@ -129,7 +113,7 @@ Automated deployment is recommended, and experienced partners can use source dep
|
|
|
|
|
|
`sh install.sh`
|
|
|
|
|
|
-- Use the jps command to see if the service is started (jps comes with Java JDK)
|
|
|
+- Use the `jps` command to check if the services are started (`jps` comes from `Java JDK`)
|
|
|
|
|
|
```aidl
|
|
|
MasterServer ----- Master Service
|
|
|
@@ -138,7 +122,8 @@ Automated deployment is recommended, and experienced partners can use source dep
|
|
|
ApiApplicationServer ----- API Service
|
|
|
AlertServer ----- Alert Service
|
|
|
```
|
|
|
-If there are more than five services, the automatic deployment is successful
|
|
|
+
|
|
|
+If all services are normal, the automatic deployment is successful
|
|
|
|
|
|
|
|
|
After successful deployment, the log can be viewed and stored in a specified folder.
|
|
|
@@ -164,49 +149,46 @@ After downloading the release version of the source package, unzip it into the r
|
|
|
|
|
|
* View directory
|
|
|
|
|
|
-After normal compilation, target/escheduler-{version}/ is generated in the current directory
|
|
|
-
|
|
|
-
|
|
|
-
|
|
|
+After normal compilation, ./target/escheduler-{version}/ is generated in the current directory
|
|
|
|
|
|
|
|
|
### 2.3 Start-and-stop services commonly used in systems (for service purposes, please refer to System Architecture Design for details)
|
|
|
|
|
|
-* stop all services in the cluster at one click
|
|
|
+* stop all services in the cluster
|
|
|
|
|
|
` sh ./bin/stop_all.sh`
|
|
|
|
|
|
-* one click to open all services in the cluster
|
|
|
+* start all services in the cluster
|
|
|
|
|
|
` sh ./bin/start_all.sh`
|
|
|
|
|
|
-* start and stop Master
|
|
|
+* start and stop one master server
|
|
|
|
|
|
```start master
|
|
|
sh ./bin/escheduler-daemon.sh start master-server
|
|
|
sh ./bin/escheduler-daemon.sh stop master-server
|
|
|
```
|
|
|
|
|
|
-* start and stop Worker
|
|
|
+* start and stop one worker server
|
|
|
|
|
|
```start worker
|
|
|
sh ./bin/escheduler-daemon.sh start worker-server
|
|
|
sh ./bin/escheduler-daemon.sh stop worker-server
|
|
|
```
|
|
|
|
|
|
-* start and stop Api
|
|
|
+* start and stop api server
|
|
|
|
|
|
```start Api
|
|
|
sh ./bin/escheduler-daemon.sh start api-server
|
|
|
sh ./bin/escheduler-daemon.sh stop api-server
|
|
|
```
|
|
|
-* start and stop Logger
|
|
|
+* start and stop logger server
|
|
|
|
|
|
```start Logger
|
|
|
sh ./bin/escheduler-daemon.sh start logger-server
|
|
|
sh ./bin/escheduler-daemon.sh stop logger-server
|
|
|
```
|
|
|
-* start and stop Alert
|
|
|
+* start and stop alert server
|
|
|
|
|
|
```start Alert
|
|
|
sh ./bin/escheduler-daemon.sh start alert-server
|
|
|
@@ -214,7 +196,7 @@ sh ./bin/escheduler-daemon.sh stop alert-server
|
|
|
```
|
|
|
|
|
|
## 3、Database Upgrade
|
|
|
-Database upgrade is a function added in version 1.0.2. The database can be upgraded automatically by executing the following commands
|
|
|
+Database upgrade is a function added in version 1.0.2. The database can be upgraded automatically by executing the following command:
|
|
|
|
|
|
```upgrade
|
|
|
sh ./script/upgrade_escheduler.sh
|
bao liang