Details
-
Feature
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
We assume that the JobScheduler is operated in a cluster and that multiple JobScheduler cluster members use the same jobs.
- Current Situation
- The task history of a job lists only the logs of the job if it was started from the current JobScheduler instance.
- Desired Situation
- The task history of a job lists all logs of the job independent from the cluster member by which it was started.
- The task history tab has the new column "Member" where you see the JobScheduler cluster member (host:port) which has started the job.
JOC expects a new attribute member in the <history.entry> element of the JobScheduler answer.