`remix-serve` isn't load balancer friendly

[joshocalico]

What version of Remix are you using?

1.7.1

Steps to Reproduce

Configure Remix to run inside an ECS container.
Setup an Application Load Balancer instance and point this at Remix.
Thrash the server, eventually (not very long after) you'll start seeing 502 errors!
This causes a failed health check from ALB and the container dies, or in this case is savagely murdered by the load balancer.

Expected Behavior

These 502s shouldn't occur.

Remix should have an option to configure the default keepAliveTimeout.

Actual Behavior

The socket gets closed by Remix, which then causes the load balancer to panic!

Silly brittle things they are.

[joshocalico]

For more info and a proposed solution:

• This is a known issue in NextJS too.
  https://nextjs.org/docs/api-reference/cli#keep-alive-timeout
• While I recognise this framework tends towards functions, it does support fixed compute too of course. Some non-AWS services don't have configurable upstream timeouts so it should be able to be implemented without having to use the ejector seat. i.e. a custom server.

I propose a config key and a CLI flag.

I'll try to implement this into remix-serve and add a caveat to the gotchas page.

[joshocalico]

Might take me a few days as I'm pretty busy, but I'll get to it if I can.
Feel free to swoop in if you have more time 🙂

[machour]

As if this a feature request, I'm going to convert it to a Proposal