This is an automated email from the ASF dual-hosted git repository.
zhangliang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere-elasticjob.git
The following commit(s) were added to refs/heads/master by this push:
new ec6aa9e For 1179 high-availability.en.md & web-console.en.md (#1180)
ec6aa9e is described below
commit ec6aa9e2406ac529035f47b3c9d81db264a95d0b
Author: 于玉桔 <[email protected]>
AuthorDate: Mon Jul 20 10:28:14 2020 +0800
For 1179 high-availability.en.md & web-console.en.md (#1180)
---
.../operation/high-availability.en.md | 21 ++++++++++++++++++++-
.../elasticjob-cloud/operation/web-console.en.md | 19 ++++++++++++++++++-
2 files changed, 38 insertions(+), 2 deletions(-)
diff --git
a/docs/content/user-manual/elasticjob-cloud/operation/high-availability.en.md
b/docs/content/user-manual/elasticjob-cloud/operation/high-availability.en.md
index ba590d7..319185b 100755
---
a/docs/content/user-manual/elasticjob-cloud/operation/high-availability.en.md
+++
b/docs/content/user-manual/elasticjob-cloud/operation/high-availability.en.md
@@ -4,4 +4,23 @@ weight = 2
chapter = true
+++
-TODO
+## Introduction
+
+The high availability of the scheduler is achieved by running several
ElasticJob-Cloud-Scheduler instances pointing to the same ZooKeeper cluster.
+ZooKeeper is used to perform leader election when the current primary
ElasticJob-Cloud-Scheduler instance fails.
+At least two scheduler instances are used to form a cluster. Only one
scheduler instance in the cluster provides services, and the other instances
are in the `standby` state.
+When the instance fails, the cluster will elect one of the remaining instances
to continue providing services.
+
+## Configuration
+
+Each ElasticJob-Cloud-Scheduler instance must use the same ZooKeeper cluster.
+For example，if the Quorum of ZooKeeper is
zk://1.2.3.4:2181,2.3.4.5:2181,3.4.5.6:2181/elasticjob-cloud，the ZooKeeper
related configuration in `elasticjob-cloud-scheduler.properties` is:
+
+```properties
+# ElasticJob-Cloud's ZooKeeper address
+zk_servers=1.2.3.4:2181,2.3.4.5:2181,3.4.5.6:2181
+
+# ElasticJob-Cloud's ZooKeeper namespace
+zk_namespace=elasticjob-cloud
+```
+
diff --git
a/docs/content/user-manual/elasticjob-cloud/operation/web-console.en.md
b/docs/content/user-manual/elasticjob-cloud/operation/web-console.en.md
index 543cc54..709e9d0 100755
--- a/docs/content/user-manual/elasticjob-cloud/operation/web-console.en.md
+++ b/docs/content/user-manual/elasticjob-cloud/operation/web-console.en.md
@@ -4,4 +4,21 @@ weight = 3
chapter = true
+++
-TODO
+The operation and maintenance platform is embedded in the jar package of
elasticjob-cloud-scheduler, and there is no need to start an additional WEB
server.
+The startup port can be adjusted by modifying the http_port parameter in the
configuration file. The default port is 8899 and the access address is
`http://{your_scheduler_ip}:8899`.
+
+## Log in
+
+Two types of accounts are provided, administrator and guest. The administrator
has all operation permissions, and the visitor only has viewing permissions.
+The default administrator user name and password are root/root, and the guest
user name and password are guest/guest. You can modify the administrator and
guest user names and passwords through `conf\auth.properties`.
+
+## Function list
+
+- Application management (publish, modify, view)
+- Job management (register, modify, view and delete)
+- View job status (waiting to run, running, pending failover)
+- Job history view (running track, execution status, historical dashboard)
+
+## Design concept
+
+The operation and maintenance platform uses pure static HTML + JavaScript to
interact with the back-end RESTful API. It displays the job configuration and
status by reading the job registry, the database displays the job running track
and execution status, or updates the job registry data to modify the job
configuration.
\ No newline at end of file
