Connection Limits / Prioritization about tracker HOT 6 CLOSED

Yes for ref too:

https://pauladamsmith.com/blog/2016/04/max-clients-go-net-http.html

from tracker.

A bit more abstract (not regarding connections etc.)

A bit of capacity must be reserved for:

1. Responses to /ping
2. Telling clients that the node is at its limits

(1) is important to prevent AWS from taking off the heavy loaded nodes
(2) is to turn undefined ELB 502 errors into defined HTTP 503 overloaded errors

from tracker.

Ok so de we queue the responses? or just 503? Sounds like 503?

from tracker.

Ok so de we queue the responses? or just 503? Sounds like 503?

Just 503 and 'Retry-After' header (if the defined limits of a route, e.g. /tr/ are reached)

PS: At least that's our current NGINX behaviour

from tracker.

Ok gotta think best way to implement this. Not sure I like what I've seen so far.

from tracker.

done

from tracker.