You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The worker is queuing requests internally. Like the worker accepts a job, hands it to the child process pool, and the pool enqueues it. That shouldn't be happening
It looks like we had some errors and then maybe timeouts after logs?
Mutchi mentioned a postgres bug around this time
Suspicion 1: Child processes are dying and not being recreated (but maybe they;'re managing to send out an error to the worker so that the queue is getting freed up)
Suspicion 2: Postgres is erroring and calling process.exit(), and the exit is not properly handled
The text was updated successfully, but these errors were encountered:
In production this afternoon we had a nasty case of worker death
Link to logs
A couple of things to note:
Suspicion 1: Child processes are dying and not being recreated (but maybe they;'re managing to send out an error to the worker so that the queue is getting freed up)
Suspicion 2: Postgres is erroring and calling process.exit(), and the exit is not properly handled
The text was updated successfully, but these errors were encountered: