Add que_jobs.created_at ?

[joevandyk]

Not sure if it would be helpful to have a timestamp that indicates when the job was created. Possibly when it was last ran as well.

I suppose you could figure that out from the retry count and the retry interval though..

Thoughts?

[chanks]

I thought a while ago about adding the usual created_at and updated_at (effectively ran_at) timestamps, but felt that all the information I'd really want out of them I'd already be getting from the error_count. I'm open to adding them if you can think of a case where they'd be useful. I'm generally hesitant to make the jobs table any wider than it needs to be, but it's only 16 bytes.

[ivawzh]

I want to regularly run a health check to see if workers are frozen. My plan is to query count of jobs which are created more than 20 mins ago. If returned number is not 0, I would assume workers not healthy. Is there anyway you can achieve the same check with run_at but not missing the never ran jobs? Cheers.

[chanks]

You can add your own created_at column if you really want to (ALTER TABLE que_jobs ADD COLUMN created_at NOT NULL DEFAULT now() should do it). I
don't see any reason it would interfere with normal operation.

On Monday, October 17, 2016, Ivan Wang notifications@github.com wrote:

I want to regularly run a health check in question to see if workers are
frozen. My plan is query count of jobs which are created more than 20 mins
ago. If returned number is not 0, I would assume workers not healthy. Is
there anyway you can achieve the same check with run_at but not missing the
never ran jobs? Cheers.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#33 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASUGr0Dkjec8vRhl0JRz5o6imfOKKzDks5q0x3wgaJpZM4BogUZ
.