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 94f7d97 Translate resource.en.md (#1145)
94f7d97 is described below
commit 94f7d97e701e942901b65873cb8c4151881c393d
Author: Tboy <[email protected]>
AuthorDate: Sat Jul 18 21:27:43 2020 +0800
Translate resource.en.md (#1145)
---
docs/content/features/resource.en.md | 37 +++++++++++++++++++++++++++++++++++-
1 file changed, 36 insertions(+), 1 deletion(-)
diff --git a/docs/content/features/resource.en.md
b/docs/content/features/resource.en.md
index c93adf5..3b99387 100644
--- a/docs/content/features/resource.en.md
+++ b/docs/content/features/resource.en.md
@@ -5,4 +5,39 @@ weight = 3
chapter = true
+++
-TODO
+The resource allocation function is unique to ElasticJob-Cloud.
+
+## Execution mode
+
+ElasticJob-Cloud is divided into two execution modes: transient and daemon
execution.
+
+### Transient execution
+
+The resources are released immediately after the execution of each job to
ensure that the existing resources are used for staggered execution.
+Resource allocation and container startup both take up a certain amount of
time, and resources may not be sufficient during job execution, so job
execution may be delayed.
+Transient execution is suitable for jobs with long intervals, high resource
consumption and no strict requirements on execution time.
+
+### Daemon execution
+
+Whether it is running or waiting to run, it always occupies the allocated
resources, which can save too many container startup and resource allocation
costs, and is suitable for jobs with short intervals and stable resource
requirements.
+
+## Scheduler
+
+ElasticJob-Cloud is developed based on the Mesos Framework and is used for
resource scheduling and application distribution. It needs to be started
independently and provides services.
+
+## Job Application
+
+Refers to the application after the job is packaged and deployed, and
describes the basic information such as the CPU, memory, startup script, and
application download path that are needed to start the job.
+Each job application can contain one or more jobs.
+
+## Job
+
+That is, the specific tasks that are actually run share the same job ecology
as ElasticJob-Lite.
+The job application must be registered before registering the job.
+
+## Resource
+
+Refers to the CPU and memory required to start or run a job.
+Configuration in the job application dimension indicates the resources needed
for the entire application to start;
+Configuration in the job dimension indicates the resources required for each
job to run.
+The resources required for job startup are the sum of the resources required
by the specified job application and the resources required by the job.
