Hi everybody, Sorry for the double post! I wanted to let you know an issue already exists for this problem: http://code.google.com/p/googleappengine/issues/detail?id=2396. I'm still unsure if it's because we are using the API incorrectly or if this is really a bug.
In the last few days, I've been trying to reduce the running time of my tasks by splitting them even more. I realized that some of them did timeout occasionally. They would eventually succeed, because failed tasks are re-executed by the engine, but strangely those URLs did fail very often with "Request was aborted..." (>40% of all requests failed like this). I started to wonder if they were somehow marked as being "bad" by the engine because they are long-running. Other faster URL would occasionally fail, but the rate was much smaller. If we take a look at these URL (data taken directly from my dashboard): Task A, "Request was aborted..." error rate (45%) (running time > 15s, will sometimes fail due to timeouts) Task B, "Request was aborted..." error rate (4.8%) (running time < 200ms ) Task C, "Request was aborted..." error rate (18%) (running time 4-5s) I'm still experimenting with this, I will let you know if I'm able to reduce the error rate of Task A. I'm currently splitting all my tasks so that each of them writes to only one entity (before I would split them in groups of 30-40). Jason (Google), what are your thoughts on this? Thanks! On Jan 18, 10:05 am, Marc Provost <mprov...@gmail.com> wrote: > This issue driving me crazy! I have cron jobs that must run overnight > and > I started to see this pattern about 3-4 weeks ago. I had to run the > jobs multiple times and > I still have to check them every morning, because sometimes all of > them failed (with the same duration as you guys). Also, > I get this error at a 4-5% rate for client requests. > > Google, please let us know what is going on. > > On Jan 15, 7:48 pm, Peter Liu <tinyee...@gmail.com> wrote: > > > Also the duration is always between 10s and 11s. cpu is always 0ms. > > > On Jan 15, 4:46 pm, Peter Liu <tinyee...@gmail.com> wrote: > > > > 01-15 04:36PM 28.187 /p/tempClean 500 10081ms 0cpu_ms 0kb > > > > Error in last 17 hours: 51 5.4% > > > > Job run every minute, it query a kind and delete the entries. > > > Currently there's no entry so the task just do a simple query. There's > > > no other traffic either. > > > > On Dec 14 2009, 4:11 am, Abhi <abhinavbhag...@gmail.com> wrote: > > > > > Sometimes my cron jobs fail with a HTTP 500 error and message:- > > > > > Request was aborted after waiting too long to attempt to service your > > > > request. Most likely, this indicates that you have reached your > > > > simultaneous dynamic request limit. This is almost always due to > > > > excessively high latency in your app. Please > > > > seehttp://code.google.com/appengine/docs/quotas.htmlformoredetails. > > > > > When this happens the logs show that the job took about 10086ms of CPU > > > > time. The cron is the only job running in the application and it fires > > > > one request every 5 minutes. I don't see any reason of why the quota > > > > for simultaneous request should be exceed by this one req/5 minutes > > > > application. There is nothing else this application is doing. > > > > > If i access the same page (which has admin only permissions - so i am > > > > sure no one else can access it) from a browser it never fails. > > > > > Can someone help me with this?
-- 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.
