DelayedJob: run_at seems to override priority

With DelayedJob, If there's a big backlog of jobs and the workers can't keep up to run the jobs at their specified times, it seems DJ selects the earliest run time over priority.

As you can see from the attached image, a job was locked at a time later than those run_at's but it chose the earlier run_at instead of the higher priority.

I would expect it to do the opposite.

Answers


You seem to use Priority backwards. Lower numbers actually have higher priority. So it looks okay to me.

Quote from https://github.com/collectiveidea/delayed_job

By default all jobs are scheduled with priority = 0, which is top priority. You can change this by setting Delayed::Worker.default_priority to something else. Lower numbers have higher priority.


Need Your Help

Powershell: Loop through existing variables to make certain ones invisible

windows variables powershell foreach

My dilemma is I want to go through all my powershell variables, and for certain ones make them invisible. I'm trying to avoid writing the code for each individual variable as there are quite a few of

Urls /lpt1 and /com1 cause IIS to render its own screen of death

iis iis-7.5

When running a recent SkipFish scan - we found that IIS (7.5) returns the following if you call /lptX or /comX (where X is a number 1-9).