So today I discovered that there's a cron job that holds non-reproducible state that died, and now our system is fucked.

The cron job doesn't live inside any source control. This morning it entered a terminal state, and because it overwrites its state there's no way to revert it.

I'm currently waiting for the database rollback and have rewritten it in a reproducible/idempotent way.

you are viewing a single comment's thread
view the rest of the comments
[–] 17 points 1 year ago

We have a couple of those at work. Black boxes that are used.

I'm rebuilding one after it failed on one morning for SQL odbc reasons. And its just a binary that shuffles data around.

  • source