Configuring Component Job Settings

Non-indexed: A job is considered complete when all the pods are successfully executed. Each pod completion is homologous to each other.
Indexed: Each pod gets an associated completion index from 0 to the number of pods minus 1. The job is considered complete when every pod allocated with an index is successfully executed. For an indexed job, pods are named in the format of ${job-name}-${index}.

ServiceStage allows you to configure job settings of a container-deployed component whose Workload Type is Job to ensure efficient and reliable batch processing. You can configure job parameters to implement flexible task management and resource optimization.

You can configure job settings of a component whose Workload Type is Job when configuring Advanced Settings.

Configuring Component Job Settings

Choose Advanced Settings > Job.

Set job parameters by referring to the following table.

Parameter	Description
Parallel Pods	Maximum number of pods that can run in parallel during job execution. The value cannot be greater than the total number of pods in the job.
Timeout (s)	Once a job reaches this time, the job status becomes failed and all pods in this job will be deleted. If you leave this parameter blank, the job will never time out.
Completion Mode	Non-indexed: A job is considered complete when all the pods are successfully executed. Each pod completion is homologous to each other. Indexed: Each pod gets an associated completion index from 0 to the number of pods minus 1. The job is considered complete when every pod allocated with an index is successfully executed. For an indexed job, pods are named in the format of ${job-name}-${index}.
Suspend Job	By default, a job is executed immediately after being created. Enabled: The job is in the suspended state after being created. Disabled: The job is executed after being created.