Skip to content

Commit 50de3e3

Browse files
Ratulac-AzureRatulac-Azure
committed
edits
1 parent de35b7c commit 50de3e3

File tree

2 files changed

+21
-21
lines changed

2 files changed

+21
-21
lines changed

‎articles/spring-apps/enterprise/concept-job.md

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "Job in Azure Spring Apps"
3-
description: Explain the Job concept in Azure Spring Apps.
3+
description: Learn more about the Job concept in Azure Spring Apps.
44
author: KarlErickson
55
ms.author: ninpan
66
ms.service: spring-apps
@@ -20,36 +20,36 @@ ms.custom: devx-track-java, devx-track-extended-java
2020

2121
*Job* is a key concept in the resource model of Azure Spring Apps. Like *App* in Azure Spring Apps, both are considered resources managed within the Service.
2222

23-
Comparing with *App* which runs the workload continuously, *Job* enables customers to run workloads that complete in finite duration. Examples of apps include web apps and background services that process input continuously, while examples of jobs include batch processes and on demand tasks.
23+
While *App* runs the workload continuously, *Job* enables customers to run workloads that complete within a finite duration. Examples of apps include web apps and background services that process input continuously, and examples of jobs include batch processes and on-demand tasks.
2424

25-
Spring developers who writes jobs propbably choose the Spring Batch framework or Spring Cloud Task. While Spring Batch excels in handling large-scale batch processing tasks, Spring Cloud Task is specialized for managing short-lived tasks with minimal overhead. You can run both types of them in Azure Spring Apps jobs efficiently to meet diverse requirements.
25+
Spring developers who write jobs probably choose the Spring Batch framework or Spring Cloud Task. While Spring Batch excels in handling large-scale batch processing tasks, Spring Cloud Task is specialized for managing short-lived tasks with minimal overhead. You can run both types in Azure Spring Apps jobs efficiently to meet diverse requirements.
2626

27-
## Job execution
27+
## Execute a job
2828

2929
A job execution refers to the process of running a particular task or set of tasks defined within a job. It encompasses the entire lifecycle of executing those tasks, including initializing, processing, and completing the job according to its specifications.
3030

31-
A common lifecycle of a job execution in Azure Spring Apps is from `pending`, `running` to termination status `completed` or `failed` depending on whether the execution finishes successfully or not.
31+
A common lifecycle of a job execution in Azure Spring Apps is from `pending`, `running`, to termination status `completed` or `failed` depending on whether the execution finishes successfully or not.
3232

3333
Each time the job is executed, it adopts its preset configuration from the job, with certain aspects allowing for customization to accommodate different runs.
3434

35-
In nonparallel job execution, only one instance runs at a time, whereas in parallel execution, multiple instances can run simultaneously.
35+
In nonparallel job execution, only one instance runs at a time. Whereas, in parallel execution, multiple instances can run simultaneously.
3636

37-
## Configuration
37+
## Configure a job
3838

3939
The job establishes the default configuration utilized for each execution, encompassing elements like the user application source and trigger configuration. Each execution of the job inherits the configuration, allowing certain parameters to be overridden with new values for individual executions.
4040

4141
The following table shows the configuration in job level or job execution level:
4242

43-
| Property name | Scope | Notes |
44-
|---|---|---|
45-
| Trigger type | Job | Job is supported to be triggered manually for public preview. More trigger types are supported later. |
46-
| Parallelism | Job | The count of instances of the job that executes in the same time. The default value is 1. For parallel job, you can get the index of each instance through `JOB_COMPLETION_INDEX` environment variable. |
47-
| Retry limit | Job |The maximum number of a job attempts to execution after encountering a failure or error. The default value is 0 that means the job does not retry if it fails. |
48-
| Timeout | Job |The maximum time in seconds when the job failed. You can leave it unset or set the value 0, which means the job has no timeout. |
49-
| Arguments | Job/Execution | The value of arguments specified for the execution override that of the job. |
50-
| Environment variables | Job/Execution | In key-value pairs format. The environment variables specified in job level are default values for each execution. The environment variables specified in execution level has higher priority. You can specify part of those environment variables when start an execution to override the value in job level. |
51-
| Secret environment variables | Job/Execution | Contain credential, the secret values are encrypted. |
52-
| CPU | Job/Execution | The value of CPU specified for the execution override that of the job. |
53-
| Memory | Job/Execution | The value of Memory specified for the execution override that of the job. |
54-
55-
The configuration on job level applies when creating or updating the job resource, that on job execution level applies when starting a job execution.
43+
| Property name | Scope | Notes |
44+
|------------------------------|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
45+
| Trigger type | Job | The manual trigger for public preview. More trigger types are supported later. |
46+
| Parallelism | Job | The count of instances of the job that executes in the same time. The default value is 1. For parallel job, you can get the index of each instance through `JOB_COMPLETION_INDEX` environment variable. |
47+
| Retry limit | Job | The maximum number of a job attempts to execution after encountering a failure or error. The default value is 0, which means the job doesn't retry if it fails. |
48+
| Timeout | Job | The maximum time in seconds when the job failed. You can leave it unset or set the value at 0, which means the job has no timeout. |
49+
| Arguments | Job/Execution | The value of arguments specified for the execution override of the job. |
50+
| Environment variables | Job/Execution | The key-value pairs format. The environment variables specified in job level are default values for each execution. The environment variables specified in execution level have higher priority. You can specify part of those environment variables when start an execution to override the value in job level. |
51+
| Secret environment variables | Job/Execution | The credentials, where the secret values are encrypted. |
52+
| CPU | Job/Execution | The value of CPU specified for the execution override of the job. |
53+
| Memory | Job/Execution | The value of Memory specified for the execution override of the job. |
54+
55+
The configuration on job level applies when creating or updating the job resource, and configuration on job execution level applies when starting a job execution.

‎articles/spring-apps/enterprise/how-to-job-log-streaming.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -117,7 +117,7 @@ When you use the `-f/--follow` option to tail instant logs, the Azure Spring App
117117

118118
### Stream logs for a specific instance
119119

120-
Use the following command to get instance names and stream logs for a specific instance:
120+
Use the following commands to get instance names and stream logs for a specific instance:
121121

122122
```azurecli
123123
az spring job execution instance list \

0 commit comments

Comments
 (0)