I see the same thing (DeadlineExceeded) over the past couple of days with a cron job that writes a few bytes of date to a single table. It had been working fine for weeks, no code changes. Over the past 10 hours, 6% of these cron requests have failed because of the ap engine errors.
Chris On Feb 22, 12:42 pm, Anders <[email protected]> wrote: > But are not deadline exceeded errors something that happens only after > an application has been instantiated, i.e. the execution of a request > taking too long time, not including the startup time for the whole > application? > > And that Django can cause several seconds of extra delay doesn't sound > plausible. > > No, I think this is something in the GAE infrastructure itself, > independent of Java or Python etc. Google should look into it, lest > IBM will beat them with a WebSphereCloud or something like that, or > Sun Microsystem with a JavaCloud, or Sony with a PlayStationCloud, or, > God forbid, Microsoft with a DOSCloud. ;-) > > On Feb 22, 6:11 pm, GAEfan <[email protected]> wrote: > > > > > Yes, I have been getting "Deadline Exceeded" errors again, starting > > about Friday. I thought this was fixed, as I hadn't seen them for a > > while. But they are back again. :-( > > > AFAIK, it is the cold-start loading of Django that is the cause of the > > delay. -- 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.
