@Kaan Soral I think the issue cannot be adequately narrowed-down from the information provided, and with only the commonality of seeing the "Request was aborted after waiting too long to attempt to service your request." error, it's impossible to determine that the same issue is being reported by Alexandra - that's the reason why a proper issue report <https://code.google.com/p/googleappengine/issues/entry> is needed (see in that link a template).
There doesn't seem to be a basis for inferring the general statement that "AppEngine can't handle bursts well". This is especially so when the justification for the statement refers to a very specific use-case related to errors seen in a task queue with specific scaling settings. These scaling settings might be at the heart of the original issue reported at the top of the thread. Having a minimum and maximum of 1 idle instance doesn't exactly lend itself to managing every possible burst. Depending on the request pattern and start-up time, you could see strange scenarios where requests are building up in pending queues, instances are firing up and then shutting down after becoming idle, with the pending queues migrating and merging among these rapidly spawning and de-spawning instances. Requests in a rather short pending queue dealing with this potentially-volatile setup would not be seen to scale well, and many could in fact reach a timeout without getting to an instance. Again, this is a plausible explanation, but not confirmed by any real data. You can read in the docs some advice on how the scaling settings work <https://cloud.google.com/appengine/docs/scaling>, and how to best design for scaling events <https://cloud.google.com/appengine/docs/managing-resources>. Of course, as usual, if you have a specific issue, feel free to provide a report in the issue tracker <https://code.google.com/p/googleappengine/issues/entry>. On Monday, November 2, 2015 at 9:05:30 PM UTC-5, Kaan Soral wrote: > > Yes, AppEngine can't handle bursts well, so the solution is to slow things > down > > Actually, there are speed limits on a lot of things that are usually not > advertised well, if you are getting these kind of errors, try to slow > things down and see how it goes > > Slowing things down is also pretty challenging, much harder than building > stuff that will scale > > On Monday, November 2, 2015 at 6:48:57 PM UTC+3, Alexandra wrote: >> >> Hi, >> >> Did you find the reason of these errors? >> >> I also see a lot of them. The time which is elapsed is about 10 min, so >> it seems that there are tasks that are stuck for some reason in the task >> queue. >> >> Any insights on that? >> >> Thanks >> Alexandra >> >> On Saturday, April 11, 2015 at 8:02:34 PM UTC+3, Kaan Soral wrote: >>> >>> "Request was aborted after waiting too long to attempt to service your >>> request." >>> >>> I've been seeing these messages a lot lately, momentarily many requests >>> log these errors, it floods the error logs >>> >>> Anyone else? >>> >> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/a3d5858f-6d8b-4656-953a-2df06119c94c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
