-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Faktory ENT staging env doesnt seem to be set correctly by FAKTORY_ENV environment variable. #455
Comments
Logging about staging is on main but has not been released. It sounds like that error is with faktory_worker_ruby, not Faktory itself. |
Can you please include the full backtrace and any initializer code for faktory_worker_ruby? |
We have no initializer code. Backtrace:
|
You're running in puma so the Faktory client defaults to a pool of 5 connections. I'm assuming you were doing some load testing and had many puma threads pushing a lot of jobs to Faktory at the same time. It has nothing to do with staging. I've increased the default pool size from 5 to 20. Pools are lazy so it will only create 20 if you actually need that many. You can run FWR's |
It was a normal traffic event for us, but we do process a ton of traffic and a lot of that traffic pushes jobs to faktory. The weird things is the staging ENV throwing the exact same error at the exact same time.. it shouldnt have had anywhere close to the same traffic as prod. |
When
FAKTORY_ENV
is set tostaging
faktory doesn't print any logs stating it is actually in staging mode, we had assumed it was working fine until we received the same error in Production and Staging at the same time:ConnectionPool::TimeoutError: Waited 1 sec, 0/5 available.
In the backtrace, the error occured when trying to push a job to faktory which makes me think both our Prod and Staging faktory instances share the same connection limit.
The text was updated successfully, but these errors were encountered: