| 1c1 |
| < commit d35f6d901d5cba8e84eb9b7b64d69e060e7fb463 |
| --- |
| > commit 250b16e1082593636d1487ced191f831b505359e |
| 3c3 |
| < Date: Mon Oct 19 19:43:49 2020 +0800 |
| --- |
| > Date: Mon Oct 19 20:52:53 2020 +0800 |
| 5c5,9 |
| < Revise tracing document (#1602) |
| --- |
| > For checkstyle & fix typo (#1608) |
| > |
| > * Fix typo |
| > |
| > * For checkstyle |
| 7,92c11,32 |
| < diff --git a/docs/content/user-manual/elasticjob-lite/usage/event-trace/_index.en.md b/docs/content/user-manual/elasticjob-lite/usage/event-trace/_index.en.md |
| < deleted file mode 100644 |
| < index 4c337227e..000000000 |
| < --- a/docs/content/user-manual/elasticjob-lite/usage/event-trace/_index.en.md |
| < +++ /dev/null |
| < @@ -1,8 +0,0 @@ |
| < -+++ |
| < -title = "Event Trace" |
| < -weight = 3 |
| < -chapter = true |
| < -+++ |
| < - |
| < -ElasticJob provides an event tracking function, which can handle important events in the scheduling process through event subscription for query, statistics and monitor. |
| < -Now, the event subscription based on relation database is provided to record events, and developers can also extend it through SPI. |
| < diff --git a/docs/content/user-manual/elasticjob-lite/usage/event-trace/_index.cn.md b/docs/content/user-manual/elasticjob-lite/usage/tracing/_index.cn.md |
| < similarity index 100% |
| < rename from docs/content/user-manual/elasticjob-lite/usage/event-trace/_index.cn.md |
| < rename to docs/content/user-manual/elasticjob-lite/usage/tracing/_index.cn.md |
| < diff --git a/docs/content/user-manual/elasticjob-lite/usage/tracing/_index.en.md b/docs/content/user-manual/elasticjob-lite/usage/tracing/_index.en.md |
| < new file mode 100644 |
| < index 000000000..72469b711 |
| < --- /dev/null |
| < +++ b/docs/content/user-manual/elasticjob-lite/usage/tracing/_index.en.md |
| < @@ -0,0 +1,8 @@ |
| < ++++ |
| < +title = "Tracing" |
| < +weight = 3 |
| < +chapter = true |
| < ++++ |
| < + |
| < +ElasticJob provides a tracing function, which can handle important events in the scheduling process through event subscription for query, statistics and monitor. |
| < +Now, the event subscription based on relation database is provided to record events, and developers can also extend it through SPI. |
| < diff --git a/docs/content/user-manual/elasticjob-lite/usage/event-trace/java-api.cn.md b/docs/content/user-manual/elasticjob-lite/usage/tracing/java-api.cn.md |
| < similarity index 81% |
| < rename from docs/content/user-manual/elasticjob-lite/usage/event-trace/java-api.cn.md |
| < rename to docs/content/user-manual/elasticjob-lite/usage/tracing/java-api.cn.md |
| < index 5867e4636..ca18a3873 100644 |
| < --- a/docs/content/user-manual/elasticjob-lite/usage/event-trace/java-api.cn.md |
| < +++ b/docs/content/user-manual/elasticjob-lite/usage/tracing/java-api.cn.md |
| < @@ -16,5 +16,6 @@ ElasticJob-Lite 在配置中提供了 TracingConfiguration,目前支持数据 |
| < CoordinatorRegistryCenter regCenter = ...; |
| < // 初始化作业配置 |
| < JobConfiguration jobConfig = ...; |
| < - new ScheduleJobBootstrap(regCenter, jobConfig, tracingConfig).schedule(); |
| < + jobConfig.getExtraConfigurations().add(tracingConfig); |
| < + new ScheduleJobBootstrap(regCenter, jobConfig).schedule(); |
| < ``` |
| < diff --git a/docs/content/user-manual/elasticjob-lite/usage/event-trace/java-api.en.md b/docs/content/user-manual/elasticjob-lite/usage/tracing/java-api.en.md |
| < similarity index 82% |
| < rename from docs/content/user-manual/elasticjob-lite/usage/event-trace/java-api.en.md |
| < rename to docs/content/user-manual/elasticjob-lite/usage/tracing/java-api.en.md |
| < index cf730a462..f46a71df7 100644 |
| < --- a/docs/content/user-manual/elasticjob-lite/usage/event-trace/java-api.en.md |
| < +++ b/docs/content/user-manual/elasticjob-lite/usage/tracing/java-api.en.md |
| < @@ -16,5 +16,6 @@ Developers can also extend it through SPI. |
| < CoordinatorRegistryCenter regCenter = ...; |
| < // init job configuration |
| < JobConfiguration jobConfig = ...; |
| < - new ScheduleJobBootstrap(regCenter, jobConfig, tracingConfig).schedule(); |
| < +jobConfig.getExtraConfigurations().add(tracingConfig); |
| < + new ScheduleJobBootstrap(regCenter, jobConfig).schedule(); |
| < ``` |
| < diff --git a/docs/content/user-manual/elasticjob-lite/usage/event-trace/spring-boot-starter.cn.md b/docs/content/user-manual/elasticjob-lite/usage/tracing/spring-boot-starter.cn.md |
| < similarity index 100% |
| < rename from docs/content/user-manual/elasticjob-lite/usage/event-trace/spring-boot-starter.cn.md |
| < rename to docs/content/user-manual/elasticjob-lite/usage/tracing/spring-boot-starter.cn.md |
| < diff --git a/docs/content/user-manual/elasticjob-lite/usage/event-trace/spring-boot-starter.en.md b/docs/content/user-manual/elasticjob-lite/usage/tracing/spring-boot-starter.en.md |
| < similarity index 100% |
| < rename from docs/content/user-manual/elasticjob-lite/usage/event-trace/spring-boot-starter.en.md |
| < rename to docs/content/user-manual/elasticjob-lite/usage/tracing/spring-boot-starter.en.md |
| < diff --git a/docs/content/user-manual/elasticjob-lite/usage/event-trace/spring-namespace.cn.md b/docs/content/user-manual/elasticjob-lite/usage/tracing/spring-namespace.cn.md |
| < similarity index 100% |
| < rename from docs/content/user-manual/elasticjob-lite/usage/event-trace/spring-namespace.cn.md |
| < rename to docs/content/user-manual/elasticjob-lite/usage/tracing/spring-namespace.cn.md |
| < diff --git a/docs/content/user-manual/elasticjob-lite/usage/event-trace/spring-namespace.en.md b/docs/content/user-manual/elasticjob-lite/usage/tracing/spring-namespace.en.md |
| < similarity index 100% |
| < rename from docs/content/user-manual/elasticjob-lite/usage/event-trace/spring-namespace.en.md |
| < rename to docs/content/user-manual/elasticjob-lite/usage/tracing/spring-namespace.en.md |
| < diff --git a/docs/content/user-manual/elasticjob-lite/usage/event-trace/table-structure.cn.md b/docs/content/user-manual/elasticjob-lite/usage/tracing/table-structure.cn.md |
| < similarity index 100% |
| < rename from docs/content/user-manual/elasticjob-lite/usage/event-trace/table-structure.cn.md |
| < rename to docs/content/user-manual/elasticjob-lite/usage/tracing/table-structure.cn.md |
| < diff --git a/docs/content/user-manual/elasticjob-lite/usage/event-trace/table-structure.en.md b/docs/content/user-manual/elasticjob-lite/usage/tracing/table-structure.en.md |
| < similarity index 100% |
| < rename from docs/content/user-manual/elasticjob-lite/usage/event-trace/table-structure.en.md |
| < rename to docs/content/user-manual/elasticjob-lite/usage/tracing/table-structure.en.md |
| --- |
| > diff --git a/docs/content/features/elastic.en.md b/docs/content/features/elastic.en.md |
| > index ef76631fe..ae3ab67ed 100644 |
| > --- a/docs/content/features/elastic.en.md |
| > +++ b/docs/content/features/elastic.en.md |
| > @@ -14,7 +14,7 @@ ElasticJob is aware of the number of servers in an almost-real-time manner, with |
| > |
| > To execute the job in distributed servers, a job will be divided into multiple individual job items, one or some of which will be executed by the distributed servers. |
| > |
| > -For example, if a job is divided into 4 slices, and there're two servers to execute the job, then each server is assigned 2 slices, undertaking 50% of the workload, as follows. |
| > +For example, if a job is divided into 4 slices, and there are two servers to execute the job, then each server is assigned 2 slices, undertaking 50% of the workload, as follows. |
| > |
| > ![Sharding Job](https://shardingsphere.apache.org/elasticjob/current/img/elastic/sharding.png) |
| > |
| > @@ -40,7 +40,7 @@ When new job server joins, ElasticJob will be aware of it from the registry, and |
| > |
| > Configuring a larger number of sharding items than the number of servers, or better, a multiplier of the number of servers, makes it more reasonably for the job to leverage the resources, and assign the sharding items dynamically. |
| > |
| > -For example, we have 10 sharding items and there're 3 servers, the number of sharding items are server A = 0,1,2; server B = 3,4,5; server C = 6,7,8,9. |
| > +For example, we have 10 sharding items and there are 3 servers, the number of sharding items are server A = 0,1,2; server B = 3,4,5; server C = 6,7,8,9. |
| > If the server C is down, then server A = 0,1,2,3,4 and B = 5,6,7,8,9, maximizing the throughput without losing any sharding item. |
| > |
| > ## High Availability |