Java 12% of all requests (several thousand) have resulted in an error.
Not sure of the specific cause but most errors are 500 errors being returned. My biggest moan would have to be the huge increase in cpu time used which is being caused by PUT requests made to the datastore taking AGES to complete. Yesterday my resource would use approximately 300ms in total, today a single PUT (of which I have three) is taking anywhere between 300ms and 400ms - it's just not acceptable. On Sep 14, 10:25 pm, coltsith <[email protected]> wrote: > java > > % Errors last 14 hrs > ################################ > 2.9% > 2.1% > 1.4% > 1.2% > 1.1% > 0.8% > 0.6% > 0.7% > > On Sep 14, 9:59 pm, Arny <[email protected]> wrote: > > > Our data: > > appid radiodeck, java > > > ####### > > URI > > > Count > > > % Errors > > last 14 hrs > > /api/2c56a38fe84d6336b9a2099409313901/json/ > > 669 3.0% > > /api/2c56a38fe84d6336b9a2099409313901/json/station/aglyYWRpb > > 259 2.3% > > > .... > > ####### > > > We never saw that many errors yet. > > > On Sep 14, 10:45 pm, "Ikai Lan (Google)" <[email protected]> > > wrote: > > > > Can you guys list how often you guys see these? Here's some information > > > that'd be helpful for us: > > > > - What % of your requests return "Request was aborted"? Is it happening > > > at > > > specific times? Java or Python? > > > - App ID > > > > There was a latency spike around 4am > > > (http://groups.google.com/group/google-appengine-downtime-notify/brows...) > > > and a minor spike about 6 hours after that. > > > > On Tue, Sep 14, 2010 at 1:36 PM, Arny <[email protected]> wrote: > > > > We're having the same issue. > > > > > Worked fine until the maintenance, as far I remember. > > > > Now our logs are filled with: > > > > > # > > > > # 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. > > > > # > > > > > Even we do only get about 8-10 requests/sec and all our responses are > > > > memcached. > > > > > Any word from the AppEngine Team? > > > > > On Sep 14, 11:14 am, mscwd01 <[email protected]> wrote: > > > > > Hey, > > > > > > This may just be a coincidence but my average CPU time per request has > > > > > risen noticably since yesterdays maintenance. Whereas my average was > > > > > 250-300ms, it now takes on average 500-600ms. This is the exact same > > > > > resource without any changes made, so I cannot seem to work out why > > > > > this would be. Has anyone else noticed this? > > > > > > Thanks > > > > > -- > > > > 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]<google-appengine%2Bunsubscrib > > > > [email protected]> > > > > . > > > > For more options, visit this group at > > > >http://groups.google.com/group/google-appengine?hl=en. -- 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.
