> What is your application id? krisen-talk (www.krisentalk.de)
> Feel free to open a production issue There is already an issue from someone else (following this thread a lot of people are affected): http://code.google.com/p/googleappengine/issues/detail?id=7133 Johan, what's going on with GAE the last days? It doesn't feel like a PaaS in production mode. Perhaps Google should reintroduce the Beta status. ;) On Tue, Mar 13, 2012 at 3:10 PM, Johan Euphrosine <[email protected]> wrote: > What is your application id? > > Feel free to open a production issue, if you want to investigate this > offthread: > > http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue > > > On Tue, Mar 13, 2012 at 11:44 AM, Mos <[email protected]> wrote: > >> Same thing the last minutes on our app (HRD, Java, Low-Traffic, one >> instance, no new deployment, simple page just hitting MemCache): >> >> "Request was aborted after waiting too long to attempt to service your >> request." --> User sees 500er >> >> GAE-Team, what is going on the last days? In my opinion the Google App >> Engine is unreliable and looks more like a alpha- or beta- >> cloudenvrionment.... >> >> Please Google share you analysis with us. >> >> Cheers >> Mos >> >> >> >> >> >> 2012/3/13 Sébastien Tromp <[email protected]> >> >>> Hello, >>> >>> Same thing here, since around an hour ago: >>> AppID: fiveorbsgame & fiveorbsgame-test >>> >>> >>> On Tue, Mar 13, 2012 at 9:59 AM, Miroslav Genov <[email protected]>wrote: >>> >>>> I'm encountering the same issue with HR app. The spike got started in >>>> about ~1 hour from now. >>>> >>>> AppID: cmsevobg >>>> Datastore: HR >>>> >>>> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote: >>>>> >>>>> In case you're keeping track of issues thinking it's generally cleared >>>>> up: >>>>> >>>>> I'm on HR and have noticed higher latencies (couple seconds instead of >>>>> e.g. 300ms) lately and sometimes higher error rates (a few instead of >>>>> 0-3). >>>>> Yesterday over about 6 hours I got a ton of 60-second requests that threw >>>>> 500's with accompanying messages [1], usually on memcache sets hitting a >>>>> deadline exceeded. Also, over the last couple weeks I've been running 3 >>>>> instances permanently despite sometimes shutting them down manually. >>>>> Usually I get by on one just fine with bursts of 2 or 3. I've noticed >>>>> that one instance serves the majority of traffic with the other two >>>>> serving >>>>> maybe 50 requests over many hours, so the shutdown isn't aggressive >>>>> enough. >>>>> >>>>> "This request caused a new process to be started for your >>>>> application..." >>>>> + >>>>> "A problem was encountered with the process that handled this request, >>>>> causing it to exit" in the same request. >>>>> >>>>> App-id: 2dumo-hr >>>>> >>>> >>>> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote: >>>>> >>>>> In case you're keeping track of issues thinking it's generally cleared >>>>> up: >>>>> >>>>> I'm on HR and have noticed higher latencies (couple seconds instead of >>>>> e.g. 300ms) lately and sometimes higher error rates (a few instead of >>>>> 0-3). >>>>> Yesterday over about 6 hours I got a ton of 60-second requests that threw >>>>> 500's with accompanying messages [1], usually on memcache sets hitting a >>>>> deadline exceeded. Also, over the last couple weeks I've been running 3 >>>>> instances permanently despite sometimes shutting them down manually. >>>>> Usually I get by on one just fine with bursts of 2 or 3. I've noticed >>>>> that one instance serves the majority of traffic with the other two >>>>> serving >>>>> maybe 50 requests over many hours, so the shutdown isn't aggressive >>>>> enough. >>>>> >>>>> "This request caused a new process to be started for your >>>>> application..." >>>>> + >>>>> "A problem was encountered with the process that handled this request, >>>>> causing it to exit" in the same request. >>>>> >>>>> App-id: 2dumo-hr >>>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Google App Engine" group. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msg/google-appengine/-/YUHiXXkGPAgJ. >>>> >>>> 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. >>>> >>> >>> -- >>> 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. >>> >> >> -- >> 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. >> > > > > -- > Johan Euphrosine (proppy) > Developer Programs Engineer > Google Developer Relations > > -- > 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. > -- 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.
