Cavalcade-Runner
Cavalcade-Runner copied to clipboard
humanmade
Daemon for Cavalcade, a scalable WordPress jobs system.
Cavalcade has a persistent failure mode where jobs "stall" - i.e. are marked in the DB as `running` but aren't actually running. This leaves them in a limbo state where...
In the event of the database server not being reachable, or queries failing for some other reason, it would be useful if Cavalcade-Runner added log items for failures.
`Job::reschedule()` uses the value `nextrun + interval` when calculating the new time to run the job. https://github.com/humanmade/Cavalcade-Runner/blob/master/inc/class-job.php#L84 This causes the jobs to run constantly if the task is originally scheduled...
When the cavalcade service is restarted, we do two things: - Ignore the signal in any `wp cavalcade run` processes - Wait for all running workers to complete in the...
We had an interesting failure mode where our galera cluster became inaccessible for about 8-9 seconds. That was long enough for every cavalcade worker to crash, then fail starting enough...
This isn't so much an issue as something that I wanted to share for the benefit of others. I set up Cavalcade for a local site (which is powered by...
I'm running this in local docker environment and I'm hitting an error which says that database refuses connection: ``` web_1 | worker.1 | Error: SQLSTATE[HY000] [2002] Connection refused web_1 |...
Currently logging looks like this: ``` worker.1 | [11] Running wp cavalcade run 11 (wp_scheduled_auto_draft_delete a:0:{}) worker.1 | [11] Started worker worker.1 | [11] Worker status: Array worker.1 | (...
Rather than relying on stream_select() giving us the array back as associative, match which worker it is manually. Fixes humanmade/Cavalcade#6.