Two workarounds that we know of: a) make each task execution run in under 1 sec. This actually solves the problem. In practice this means respawning tasks, which is a pain, but can generally greatly improve things
b) skew the execution time average. If your tasks take 10 seconds to run, you will need to mix in a few tasks that take a very short time, to "fix" the average. We found that a no-op task can run in as little as 30-40 msec, so do your math. Chances are you will need to do both, and you will still get some 500's anyway though, but in more manageable numbers (<10%) J On Oct 2, 1:59 pm, onur <ogun...@gmail.com> wrote: > I see this issue > here:http://code.google.com/p/googleappengine/issues/detail?id=2396&colspe... > > This is actually serious. I've changed all my code to make it > parallel, but this issue ruins everything :( > should be fixed asap. > > On Oct 2, 3:48 am, onur <ogun...@gmail.com> wrote: > > > "Request was aborted after waiting too long to attempt to service your > > request. This may happen sporadically when the App Engine serving > > cluster is under unexpectedly high or uneven load. If you see this > > message frequently, please contact the App Engine team." > > > So, here I am. I got this message 9 out of 10 tasks I add. I am > > enqueueing tasks in a for loop, should I pass countdown, or is this > > just a temporary problem? Tasks run eventually anyway, but sometimes > > they are way late than they should be. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
