In larger environments that get a decent amount of traffic, it's important that the node keepAliveTimeout & headersTimeout are able to be set (the default is 5s for keepAliveTimeout). Currently the only way to do that is to add it to the generated file post-build (fragile), or create a whole new preset on your own (and lose all of the great stuff already in the current preset)
In our prod env (50+ servers), we were getting tens of thousands of 502's per day because the node keepAliveTimeout was so low compared to our Application Load Balancer idleTimeout (30s)
Describe the feature
In larger environments that get a decent amount of traffic, it's important that the node
keepAliveTimeout
&headersTimeout
are able to be set (the default is 5s forkeepAliveTimeout
). Currently the only way to do that is to add it to the generated file post-build (fragile), or create a whole new preset on your own (and lose all of the great stuff already in the current preset)In our prod env (50+ servers), we were getting tens of thousands of 502's per day because the node
keepAliveTimeout
was so low compared to our Application Load BalanceridleTimeout
(30s)related: https://github.com/nuxt/nuxt/issues/18857 https://github.com/nuxt/nuxt/issues/9740
Additional information