5.2.4 Killing of service linkage jobs
The following table shows the operation when a service linkage job is killed and when the timeout time is reached.
|
Target |
Status |
|
|---|---|---|
|
Manager |
Job on the scheduler service |
The status of the service linkage job turns to "kill". |
|
Execution destination (Agent) |
Service linkage job |
The system forcibly terminates the process of the service linkage job execution program. |
|
Command |
The command process continues operating. |
|
|
Linked cloud service |
The status remains as it was before the forced termination of the service linkage job. |
|
Depending on when killing occurs, the status of a request to the linked cloud service may be unknown. Because of this, check the execution status of the job on the job execution destination and the status of linked cloud service, and take actions as needed.
The following describes how to take actions.
- Actions on the service linkage job execution host
-
When there are unnecessary files on the job execution host, delete them as needed.
The command executed by the service linkage job may still remain running. Therefore, check the command execution status on the job execution host by following the steps below, and forcibly terminate it.
-
Find the process ID of the command from the log of the execution program of the service linkage job.
-
Check the command execution status from the process ID and execution file name by using, for instance, an OS command.
-
- Actions to the linked cloud service
-
Stop the cloud service as needed because a server-less application may be running.
For details on how to check the status of the linked cloud service, see 8.5.3 Troubleshooting failures of jobs and linked cloud services.
- Note
-
In the case that multiple executions are not permitted with the linked cloud service and the command defined in the service linkage execution definitions activated, if you re-execute a service linkage job that has been forcibly terminated or reached the termination time, the job may not be executed immediately or an error may occur.
Stop the linked cloud service or the command before re-executing the service linkage job.