Details
-
Feature
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
Current Situation
- If task is terminated due to timeout then the JobScheduler writes the following to the log:
[ERROR] SCHEDULER-272 Terminating task after reaching deadline <job timeout="30"> [ERROR] Z-REMOTE-122 Separate process pid=5468: Caller has killed process / zschimmer::com::object_server::Connection::pop_operation [ERROR] SCHEDULER-202 Connection to task has been lost, state=ending: Z-REMOTE-122 Separate process pid=5468: Caller has killed process
Only the last error message in the error element is added to the <show_job/> answer:
SCHEDULER-202 Connection to task has been lost, state=ending: Z-REMOTE-122 Separate process pid=5468: Caller has killed process
- If a task is terminated due to a kill task command then the JobScheduler writes the following to the log:
[ERROR] Z-REMOTE-122 Separate process pid=5468: Caller has killed process / zschimmer::com::object_server::Connection::pop_operation [ERROR] SCHEDULER-202 Connection to task has been lost, state=ending: Z-REMOTE-122 Separate process pid=3536: Caller has killed process
Only the last error message in the error element is added to the <show_job/> answer:
SCHEDULER-202 Connection to task has been lost, state=ending: Z-REMOTE-122 Separate process pid=3536: Caller has killed process
Desired Behavior
- The error element of a <show_job/> answer should be
SCHEDULER-272 Terminating task after reaching deadline <job timeout="30">
- The error element of a <show_job/> answer should be
SCHEDULER-xxx Terminating task after <kill_task> command