[shardingsphere-elasticjob] branch master updated: fix failover doc (#1898)

[wu...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

wuweijie 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 b0a1d87  fix failover doc (#1898)
b0a1d87 is described below

commit b0a1d8784efcccfe00d0c5035c9ab0997b46e09d
Author: wangxu <wx...@126.com>
AuthorDate: Mon Jun 7 11:17:44 2021 +0800

    fix failover doc (#1898)
    
    Co-authored-by: wangxu29 <wa...@jd.com>
---
 docs/content/features/failover.cn.md                                | 2 --
 docs/content/features/failover.en.md                                | 2 --
 docs/content/user-manual/elasticjob-lite/configuration/_index.cn.md | 4 ----
 docs/content/user-manual/elasticjob-lite/configuration/_index.en.md | 4 ----
 4 files changed, 12 deletions(-)

diff --git a/docs/content/features/failover.cn.md b/docs/content/features/failover.cn.md
index 297ed6d..25768c2 100644
--- a/docs/content/features/failover.cn.md
+++ b/docs/content/features/failover.cn.md
@@ -8,8 +8,6 @@ chapter = true
 ElasticJob 不会在本次执行过程中进行重新分片，而是等待下次调度之前才开启重新分片流程。
 当作业执行过程中服务器宕机，失效转移允许将该次未完成的任务在另一作业节点上补偿执行。
 
-失效转移需要与监听作业运行时状态同时开启才可生效。
-
 ## 概念
 
 失效转移是当前执行作业的临时补偿执行机制，在下次作业运行时，会通过重分片对当前作业分配进行调整。
diff --git a/docs/content/features/failover.en.md b/docs/content/features/failover.en.md
index dc55d53..c6fc5bf 100644
--- a/docs/content/features/failover.en.md
+++ b/docs/content/features/failover.en.md
@@ -8,8 +8,6 @@ chapter = true
 ElasticJob will not re-shard during this execution, but wait for the next scheduling before starting the re-sharding process.
 When the server is down during job execution, failover allows the unfinished task to be compensated and executed on another job node.
 
-Enable failover and monitorExecution together to take effect.
-
 ## Concept
 
 Failover is a temporary compensation execution mechanism for the currently executed job. When the next job is run, the current job allocation will be adjusted through resharding.
diff --git a/docs/content/user-manual/elasticjob-lite/configuration/_index.cn.md b/docs/content/user-manual/elasticjob-lite/configuration/_index.cn.md
index 5df6223..364a783 100644
--- a/docs/content/user-manual/elasticjob-lite/configuration/_index.cn.md
+++ b/docs/content/user-manual/elasticjob-lite/configuration/_index.cn.md
@@ -76,10 +76,6 @@ ElasticJob-Lite 提供了 3 种配置方式，用于不同的使用场景。
 因为是瞬时状态，所以无必要监控。请用户自行增加数据堆积监控。并且不能保证数据重复选取，应在作业中实现幂等性。
 每次作业执行时间和间隔时间均较长的情况，建议监控作业运行时状态，可保证数据不会重复选取。
 
-**failover:**
-
-需要与 monitorExecution 同时开启才可生效。
-
 **maxTimeDiffSeconds:**
 
 如果时间误差超过配置秒数则作业启动时将抛异常。
diff --git a/docs/content/user-manual/elasticjob-lite/configuration/_index.en.md b/docs/content/user-manual/elasticjob-lite/configuration/_index.en.md
index 0e91d8c..ae5ba39 100644
--- a/docs/content/user-manual/elasticjob-lite/configuration/_index.en.md
+++ b/docs/content/user-manual/elasticjob-lite/configuration/_index.en.md
@@ -75,10 +75,6 @@ When the execution time and interval of each job are very short, it is recommend
 There is no need to monitor because it is a transient state. User can add data accumulation monitoring by self. And there is no guarantee that the data will be selected repeatedly, idempotency should be achieved in the job.
 If the job execution time and interval time are longer, it is recommended to monitor the job status, and it can guarantee that the data will not be selected repeatedly.
 
-**failover:**
-
-Enable failover and monitorExecution together to take effect.
-
 **maxTimeDiffSeconds:**
 
 If the time error exceeds the configured seconds, an exception will be thrown when the job starts.