Page Comparison

This article outlines the nominal data flow of a job though HySDS.{{Include updated diagram here}}

...

Tracking a Job

Jobs can be tracked through the job lifecycle via the payload ID. In Figaro, operators can facet on a job’s unique ID to monitor progression through the various stages as well as for troubleshooting functionality.

{{add comment about job tracking through the job lifecycle, facet on payload ID with a screenshot of the payload ID in Figaro for a specific job, highlighted in red. }}

Submit a Job

A job is submitted via On-Demand or a Trigger Rule. Once submitted it moves to job-queued status.

...

• If timedout: Jobs that have timed out are changed to job-offline status and then deleted.

• If succeeded with exit code == 0: Successfully completed jobs are updated to job-completed status. Finally, completed jobs are deleted.

• If succeeded with exit code != 0: Jobs with non-zero exit codes are associated with failed jobs. Their status is updated to job-failed and then deleted.

...

Job Deduped

...

“In figaro, there are various troubleshooting functions using payload ID to track the job through the system. Include this in the basic flow of jobs through” - Lela

...

Jobs that have identical parameters, or if the same job was already successfully completed, are deduped and no further processing occurs.

Filter by label (Content by label)
showLabels false max 5 spaces com.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@11962 showSpace false sort modified type page reverse true labels kb-how-to-article cql label = "kb-how-to-article" and type = "page" and space = "HYS"

Page Properties
hidden true
Related issues