That's great! I mis-read that comment before, and thought it had to do with a billing issue or High-replication datastore. (Mos's question appeared to be about billing, and the response seemed to indicate something with the HRD - which we are not using HRD).
I'm glad that there is actually some work going in to this... -Nathan On Thursday, March 15, 2012 1:35:27 PM UTC-6, Rick Mangi wrote: > > They have responded. Look at the last comment in the thread before yours. > I'm not trying to defend them by any means, I think the lack of response > from google in general is quite disturbing, but Ikai did reply finally > saying that they are working on it. > > On Thursday, March 15, 2012 1:59:45 PM UTC-4, toonetown wrote: >> >> Yes - we are still seeing problems too - I think it is ridiculous that we >> aren't hearing anything about the issue from Google...how they are planning >> on addressing it, etc. >> >> There are over 15 bugs that are similar to >> http://code.google.com/p/googleappengine/issues/detail?id=7133 - all >> have been logged in the past 2 weeks, so that tells me that *SOMETHING* is >> wrong... >> >> -Nathan >> >> On Wednesday, March 14, 2012 9:42:21 AM UTC-6, Mos wrote: >>> >>> Problem still exists: High latency and a significant number of requests >>> fail or result in uncontrolled creation of new instances. >>> >>> GAE customers complain and complain for days. It seems like many >>> website have to accept that the 500-error is an integral feature of the GAE >>> run-time. >>> Even worse: The broken platform leads to increase usage of instances >>> and therefore leads to higher costs for paying customer. >>> >>> No communication from Google; no feedback on the mailing list; no status >>> updates on the issue tracker. >>> Instead a always green status: http://code.google.com/status/appengine >>> >>> (I think the GAE community needs to develop a crowed sources status page to >>> get a picture what's really is going on) >>> >>> That makes me crazy. I saw many platforms and business support forums >>> the last years, but never encountered such an ignorance regarding custom >>> complains. >>> >>> The only official response I saw, was the "Escalated your issue to the >>> reliability team" in one of the related issues: >>> http://code.google.com/p/googleappengine/issues/detail?id=7133 >>> >>> So, 'realiability team' what's going on? How is the status? >>> >>> >>> >>> On Tue, Mar 13, 2012 at 3:22 PM, Mos <[email protected]> wrote: >>> >>>> > 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. >>>>> >>>> >>>> >>> > On Thursday, March 15, 2012 1:59:45 PM UTC-4, toonetown wrote: >> >> Yes - we are still seeing problems too - I think it is ridiculous that we >> aren't hearing anything about the issue from Google...how they are planning >> on addressing it, etc. >> >> There are over 15 bugs that are similar to >> http://code.google.com/p/googleappengine/issues/detail?id=7133 - all >> have been logged in the past 2 weeks, so that tells me that *SOMETHING* is >> wrong... >> >> -Nathan >> >> On Wednesday, March 14, 2012 9:42:21 AM UTC-6, Mos wrote: >>> >>> Problem still exists: High latency and a significant number of requests >>> fail or result in uncontrolled creation of new instances. >>> >>> GAE customers complain and complain for days. It seems like many >>> website have to accept that the 500-error is an integral feature of the GAE >>> run-time. >>> Even worse: The broken platform leads to increase usage of instances >>> and therefore leads to higher costs for paying customer. >>> >>> No communication from Google; no feedback on the mailing list; no status >>> updates on the issue tracker. >>> Instead a always green status: http://code.google.com/status/appengine >>> >>> (I think the GAE community needs to develop a crowed sources status page to >>> get a picture what's really is going on) >>> >>> That makes me crazy. I saw many platforms and business support forums >>> the last years, but never encountered such an ignorance regarding custom >>> complains. >>> >>> The only official response I saw, was the "Escalated your issue to the >>> reliability team" in one of the related issues: >>> http://code.google.com/p/googleappengine/issues/detail?id=7133 >>> >>> So, 'realiability team' what's going on? How is the status? >>> >>> >>> >>> On Tue, Mar 13, 2012 at 3:22 PM, Mos <[email protected]> wrote: >>> >>>> > 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 view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/5fcGA5WIF30J. 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.
