Tim, I run python + webapp. My cold starts are ~2 sec. I should mention that I have also seen this error when firing up the built in eReporter ....
For some reason I saw 3 in a row this morning. All cold starts. My cron handler is quite simple, like I said it's pythong + webapp, a few imports. I find it hard to believe it has anything to do with my app, it seems like some type of quirk with app engine right now... Most people don't see this error because for some reason it is reported as a warning, and not an error. You must adjust the severity level of your logs to see it. Any chance Google has a comment on this? Like I said, I have created "warmup" cron jobs 1 minute before my real crons and it has done the trick so far. So it's not major, but kinda embarassing when a customer sees this error... On Oct 25, 2:03 am, Tim Hoffman <[email protected]> wrote: > A quite sites will see this sort of problem, you may find you startup > time for a cron or any other handler > is quite expensive. If google infrastructure is running a bit slow, > then the startup time could blow out > hence the 500 error. > > You haven't said if your running python or java. But either way I > would include some logging so that you can see how long your app takes > on average to startup a cold instance. > > Rgds > > Tim > > On Oct 25, 11:36 am, Jamie H <[email protected]> wrote: > > > App Engine Staff, > > > I continue to receive this error on all my apps. I receive this error > > on cold starts. I say this because in the past Google has responded > > this is due to > 1 sec averages, causing Google to not scale your > > app. This is not the case for me. I receive it on 0 load. I see > > these on 3 different apps, at random times. It is most annoying when > > I receive this error on my CRON entries. Obviously, this causes cron > > to be unreliable. To get around this I have had to add "warmup" cron > > entries 1 minute before my real cron entries. I feel it is ridiculous > > for me to have to do so. Please, can somebody respond on this issue? > > I see many others in the group reporting similar findings. > > > To summarize, I understand this error can be a result of Google not > > scaling your app + too many requests and requests timing out in 10 > > second queue. This is not the case for my app. I receive it when my > > app has NO load. > > > 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. > > -- 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.
