[mistwang]

Originally Posted by IanD

The 'no connection timeout' is great for one problem but I'm still looking a solution to the

retry with new instance

problem. It don't want it to retry, I want it to hit the connection timeout and die. If it's hitting the connection timeout it means there is a problem and just retrying it only makes things worse..

In my situation with long running mysql queries anyway! I look at mytop and see 4 or 5 identical long queries running because they are from the same user and their process is just trying and retrying.

Any ideas?

I am not sure those mysql queries are caused by "retry with new instance", maybe user keep trying to load that page.

There are many cases will trigger retry with new instance, mainly due to PHP crashes or exits after finishing "PHP_MAX_REQUESTS".

"retry with new instance" is to reduce 503 error as much as possible. Will see anything can be done to avoid "retry with new instance" when possible.