I continue to see these sort of errors sporadically. Identical requests can be serviced in as shot as 23ms. It really seems like the trouble is in the cluster...
The more I search this group, the more I find threads like this that never get replied to. I also see folks that would be willing to pay for support to get answers. -s On Oct 13, 2:46 pm, troppoli <[email protected]> wrote: > I'm seeing a lot of "Request was aborted after waiting too long to > attempt to service your request" for simple tasks that typically take > 25-150 ms to be serviced. > > Most of the failures are for the simplest things that our server does, > inspect some arguments and return an XML response. There is no > calculating, external lookups or db calls for this. A few weeks ago, I > changed the max idle instances to the minimum as user latency isn't a > big issue. This app uses next to no processing power, so the change > from CPU time to instance hours results in a large percent bill > increase, but not a particularly large bill. When I noticed the volume > of errors I switched everything back to automatic yesterday, but that > has not helped, and the frequency of the errors hasn't slowed down. > The long term graph of errors per second shows that this problem seems > to have started 4 days ago, and has gotten much worse in the last 24 > hours. > > The python dashboard shows no trouble. > > this seems like an odd way of getting support.... but help. > > -s -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
