Worker Daemon

Introduction

The different steps from the https://mediahaven.atlassian.net/wiki/spaces/CS/pages/3520724993 are performed as a series of worker daemon jobs which this screen in the Monitoring reports.

The worker daemon jobs can have the following statuses

Status	Meaning	Color	Since

Status	Meaning	Color	Since
`waiting`	Job has yet to be picked up	WHITE
`processing`	A worker daemon is currently processing the job	BLUE
`pending_asynchronously`	When asynchronous jobs are picked up, their job ID is passed into the newly created linked concept (i.e. batch) and the job gets this status until the linked concept completes and the job acquires its final status `accept`/`reject` and its actual finish date.	BLUE	`25.2`
`accepted`	The job was completed and executed as expected	GREEN
`rejected`	The job was completed but the execution followed not the standard flow. For example, the job `MD5_CHECK` will finish with status `accepted` if the MD5 was the same as the expected value; it will finish with status `rejected` if the MD5 value was wrong.	ORANGE
`failed`	An unexpected issue occurred, for example, a connection timeout with the destination storage The job can be restarted by pressing the play icon next to the status `error`	RED

Worker daemon jobs have a priority which is calculated according to the rule described in Worker daemon fairness
Jobs with a higher value of priority are executed first, this is the opposite of priority Transcoding Monitoring where jobs with a lower value of priority are executed first

Screen	Description

Screen	Description
Queues	Overview of recent jobs
Jobs	Complete overview of all worker daemons jobs Completed or rejected worker daemon jobs are deleted after 30 days
Failed	Same as jobs but restricted to status `failed`
Statistics	Aggregate summary of the jobs grouped by task type This view has a heavy performance impact on the database when rendering it
Server Logs / Logging	Linking to the logging of all worker daemons

Worker daemon jobs are automatically cleaned up in the following scenarios:

Permanent deletion of a record: when a record is permanently deleted, the associated worker daemon jobs and workflows are automatically cleaned up
Stopping a workflow: when a workflow is stopped, any ongoing worker daemon jobs related to that workflow are automatically cleaned up
Once per day
- Remove all jobs that were completed or rejected more than 1 month ago
- Remove all jobs that were waiting more than 2 weeks