I just upgraded to latest warbler/rack (0.9.12/0.9.3). I’ll do some
testing on it, but wanted to run something past you …
On our last round of load testing we saw our app, TriSano go into a
predictable death spiral once it got to a certain point of load.
I’m hoping to come up with some form of a “circuit breaker” to avoid
this. What seems to happen is as threads build up and wait, the app
bleeds resources and can never recover. I realize there is a bug fixed
around this in 1.1.6 (threads / memory), but I still would like this
configured so that rather than allowing threads to build up, the circuit
breaker kicks in and we tell the user to try again later (and the thread
queue stays low).
I observed in rack 0.9.2 that the rack timeout didn’t kick in the way I
expected. Under load I couldn’t get it to reject requests. I configured
it to 5 seconds, but it wouldn’t reject requests that clearly were
waiting this long.
My real question is: is Warbler timeout a good choice for a circuit
breaker? How have you observed it to work in cases like this?
To unsubscribe from this list, please visit: