fatal error: concurrent map writes about awslambdaproxy HOT 3 CLOSED

Hi @unk2k - thanks for reporting this issue. This project was created just as a small prototype and definitely not designed to be used a high performance proxy with a large number of connections. There's a lot of work to refactor this into a real production quality solution, and that is not something I currently intend on doing, but maybe at some point in the future. Be aware that there is likely a hard limit on the number of outbound connections allowed from a single Lambda function (not sure what that is off the top of my head), so I would assume you'd be bumping into that here. The specific fatal log you posted looks like a concurrency bug (and there's probably a number of them in this current codebase). Happy to take any PRs to fix that.

from awslambdaproxy.

Easy way to reproduce

$ hey -n 5000 -c 200  -x 'http://admin:awslambdaproxy@<PROXY_IP_HERE>:8080' https://github.com/

I found that number of connections with port 8082 is growing up during the test.
from 32 at startup to 1600 at the panic error

from awslambdaproxy.

@dan-v You were right. There is a limit in 1024 file descriptors. which means that the error should be around it. I'll come back if I found something.

from awslambdaproxy.