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
Config first data timeout #1111
Conversation
There is an issue with the AWS ELB, where if the ELB's idle timeout is larger than the instance's tcp keepalive timeout, then the ELB will sometimes report back 504s to the user client. If you configure puma with this first_data_timeout setting to a value that is higher than the ELB's idle timeout, then you can circumvent that problem. This patch exposes the first_data_timeout setting to the puma DSL. I have manually tested this patch and it works as intended. |
I'm going to say this is probably blocking on getting |
Right. I don't know how to fix that. |
Heh me neither right now, sorry :) Not your fault/problem, we just need to fix that before merging. |
71ab03e
to
dbfb23b
Compare
So apparently if you add |
I don't think so, it's a deadlock that doesn't ever resolve. |
I made some notes about that test here: 43ee6dd#commitcomment-20006908 |
Alright, you know what. This is just adding a config point, your use case is valid, not a big deal. Sorry this took so long to merge. |
No description provided.