[google-appengine] Re: Instances still getting killed and causing user 500's
To paraphrase johnP, "This afternoon is a serving train-wreck." My poor unicorns' tongues are raw from gorging on Sour Skittles(tm). David On Friday, March 1, 2013 7:32:29 PM UTC-7, Cesium wrote: > > I'm sure you noticed the question on this forum that Takashi did respond > to. > > > On Friday, March 1, 2013 11:47:21 AM UTC-7, Carl Schroeder wrote: > > I am porting to Go. Then I care much less about the instance scheduler > committing unicorn genocide. > > Almost done. > > > > > > RIP GAE/J, thanks for wasting my dev time replacing you! > > > > > > On Friday, March 1, 2013 9:28:13 AM UTC-8, johnP wrote:This morning is a > serving train-wreck here, too. > > > > > > > > > > > > > > On Wednesday, February 27, 2013 7:50:47 AM UTC-8, Kinesh Patel wrote:On > Python 2.7 paid app. Setting an idle instance seems to mitigate this, but > every time a new dynamic instance is spawned or hit i get this problem. > Definitely not normal behavior. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Instances still getting killed and causing user 500's
I'm sure you noticed the question on this forum that Takashi did respond to. On Friday, March 1, 2013 11:47:21 AM UTC-7, Carl Schroeder wrote: > I am porting to Go. Then I care much less about the instance scheduler > committing unicorn genocide. > Almost done. > > > RIP GAE/J, thanks for wasting my dev time replacing you! > > > On Friday, March 1, 2013 9:28:13 AM UTC-8, johnP wrote:This morning is a > serving train-wreck here, too. > > > > > > > On Wednesday, February 27, 2013 7:50:47 AM UTC-8, Kinesh Patel wrote:On > Python 2.7 paid app. Setting an idle instance seems to mitigate this, but > every time a new dynamic instance is spawned or hit i get this problem. > Definitely not normal behavior. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Instances still getting killed and causing user 500's
I am porting to Go. Then I care much less about the instance scheduler committing unicorn genocide. Almost done. RIP GAE/J, thanks for wasting my dev time replacing you! On Friday, March 1, 2013 9:28:13 AM UTC-8, johnP wrote: > > This morning is a serving train-wreck here, too. > > > > > On Wednesday, February 27, 2013 7:50:47 AM UTC-8, Kinesh Patel wrote: >> >> On Python 2.7 paid app. Setting an idle instance seems to mitigate this, >> but every time a new dynamic instance is spawned or hit i get this problem. >> Definitely not normal behavior. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Instances still getting killed and causing user 500's
This morning is a serving train-wreck here, too. On Wednesday, February 27, 2013 7:50:47 AM UTC-8, Kinesh Patel wrote: > > On Python 2.7 paid app. Setting an idle instance seems to mitigate this, > but every time a new dynamic instance is spawned or hit i get this problem. > Definitely not normal behavior. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Instances still getting killed and causing user 500's
I have sacrificed several unicorns and prayed fervently to the Google Gods, but this morning instances are thrashing badly; living no more than a minute or so. Google really needs to figure out the underlying issue, and also start communicating with their customers more effectively. The awesome power and features of App Engine will soon not be enough for us to suffer through this on an ongoing basis. On Wednesday, February 27, 2013 8:10:37 PM UTC-5, Cesium wrote: > > > Starting about 16:30 Pacific time, my Java HRD Instances were shutting > down after just a few seconds. > > Just as my rage reached class IV, serving returned to normal. > > I know this is an overreaction, but I may have to sacrifice a unicorn. > > Please, please, App Engine team, spare Mr. Sparkles. > > > This is disheartening, > David > > On Wednesday, February 27, 2013 11:32:07 AM UTC-7, Chris Tan wrote: > > I'm also getting this problem. > > > > On Wednesday, February 27, 2013 7:50:47 AM UTC-8, Kinesh Patel wrote:On > Python 2.7 paid app. Setting an idle instance seems to mitigate this, but > every time a new dynamic instance is spawned or hit i get this problem. > Definitely not normal behavior. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Re: Instances still getting killed and causing user 500's
Hello Takashi, any feedback for us? Cheers Mos On Thu, Feb 28, 2013 at 1:06 PM, Mos wrote: > Trust me; Google has no clue what's going on. > The instance scheduler went crazy, people have downtimes and have > increased billing (for weeks!) > > If Google would be able to track the problem (or would have a clue how > to fix it), > they would give a comment. > > As I wrote. That's not the first time. Last year we had the same > situation for weeks. > Google is not learning from past faults. That's the biggest problem. > Check the latest comments of last years issue: > http://code.google.com/p/googleappengine/issues/detail?id=8004 > > I think it is important to make this behavior public. And I hope the press > will tell the story. > All in all GAE is not a priority product of Google and I'm sure that > it is out of business in the next five years! > > > On Thu, Feb 28, 2013 at 4:23 AM, Prashant Hegde > wrote: >> Many apps are hitting the same issue, starring the following may increase >> chances of getting resolution. The app engine performance is unpredictable. >> Right now, as far as we are concerned, the most effective solution is to >> offer prayers very sincerely every morning. >> >> http://code.google.com/p/googleappengine/issues/detail?id=8781 >> >> This issue has been around for a few weeks with no resolution or any >> semblance of activity. >> >> Prashant >> >> >> >> >> >> On Thu, Feb 28, 2013 at 7:15 AM, Cesium wrote: >>> >>> Oh Joy, >>> >>> Now the console charts have been erased. >>> >>> I'm losing it. >>> >>> Unicorn liver pate for dinner. >>> >>> David >>> >>> >>> >>> On Wednesday, February 27, 2013 6:10:37 PM UTC-7, Cesium wrote: >>> > Starting about 16:30 Pacific time, my Java HRD Instances were shutting >>> > down after just a few seconds. >>> > >>> > Just as my rage reached class IV, serving returned to normal. >>> > >>> > I know this is an overreaction, but I may have to sacrifice a unicorn. >>> > >>> > Please, please, App Engine team, spare Mr. Sparkles. >>> > >>> > >>> > This is disheartening, >>> > David >>> > >>> > On Wednesday, February 27, 2013 11:32:07 AM UTC-7, Chris Tan wrote: >>> > > I'm also getting this problem. >>> > > >>> > > On Wednesday, February 27, 2013 7:50:47 AM UTC-8, Kinesh Patel >>> > > wrote:On Python 2.7 paid app. Setting an idle instance seems to mitigate >>> > > this, but every time a new dynamic instance is spawned or hit i get this >>> > > problem. Definitely not normal behavior. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Google App Engine" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to google-appengine+unsubscr...@googlegroups.com. >>> To post to this group, send email to google-appengine@googlegroups.com. >>> Visit this group at http://groups.google.com/group/google-appengine?hl=en. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to google-appengine+unsubscr...@googlegroups.com. >> To post to this group, send email to google-appengine@googlegroups.com. >> Visit this group at http://groups.google.com/group/google-appengine?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Re: Instances still getting killed and causing user 500's
Mos makes some good points and states them clearly. However, my idea of Faith Based Scheduler Maintenance seems to be yielding pretty good results. David On Thursday, February 28, 2013 5:06:00 AM UTC-7, Mos wrote: > Trust me; Google has no clue what's going on. > > The instance scheduler went crazy, people have downtimes and have > > increased billing (for weeks!) > > > > If Google would be able to track the problem (or would have a clue how > > to fix it), > > they would give a comment. > > > > As I wrote. That's not the first time. Last year we had the same > > situation for weeks. > > Google is not learning from past faults. That's the biggest problem. > > Check the latest comments of last years issue: > > http://code.google.com/p/googleappengine/issues/detail?id=8004 > > > > I think it is important to make this behavior public. And I hope the press > > will tell the story. > > All in all GAE is not a priority product of Google and I'm sure that > > it is out of business in the next five years! > > > > > > On Thu, Feb 28, 2013 at 4:23 AM, Prashant Hegde > > wrote: > > > Many apps are hitting the same issue, starring the following may increase > > > chances of getting resolution. The app engine performance is unpredictable. > > > Right now, as far as we are concerned, the most effective solution is to > > > offer prayers very sincerely every morning. > > > > > > http://code.google.com/p/googleappengine/issues/detail?id=8781 > > > > > > This issue has been around for a few weeks with no resolution or any > > > semblance of activity. > > > > > > Prashant > > > > > > > > > > > > > > > > > > On Thu, Feb 28, 2013 at 7:15 AM, Cesium wrote: > > >> > > >> Oh Joy, > > >> > > >> Now the console charts have been erased. > > >> > > >> I'm losing it. > > >> > > >> Unicorn liver pate for dinner. > > >> > > >> David > > >> > > >> > > >> > > >> On Wednesday, February 27, 2013 6:10:37 PM UTC-7, Cesium wrote: > > >> > Starting about 16:30 Pacific time, my Java HRD Instances were shutting > > >> > down after just a few seconds. > > >> > > > >> > Just as my rage reached class IV, serving returned to normal. > > >> > > > >> > I know this is an overreaction, but I may have to sacrifice a unicorn. > > >> > > > >> > Please, please, App Engine team, spare Mr. Sparkles. > > >> > > > >> > > > >> > This is disheartening, > > >> > David > > >> > > > >> > On Wednesday, February 27, 2013 11:32:07 AM UTC-7, Chris Tan wrote: > > >> > > I'm also getting this problem. > > >> > > > > >> > > On Wednesday, February 27, 2013 7:50:47 AM UTC-8, Kinesh Patel > > >> > > wrote:On Python 2.7 paid app. Setting an idle instance seems to > >> > > mitigate > > >> > > this, but every time a new dynamic instance is spawned or hit i get > >> > > this > > >> > > problem. Definitely not normal behavior. > > >> > > >> -- > > >> You received this message because you are subscribed to the Google Groups > > >> "Google App Engine" group. > > >> To unsubscribe from this group and stop receiving emails from it, send an > > >> email to google-appengine+unsubscr...@googlegroups.com. > > >> To post to this group, send email to google-appengine@googlegroups.com. > > >> Visit this group at http://groups.google.com/group/google-appengine?hl=en. > > >> For more options, visit https://groups.google.com/groups/opt_out. > > >> > > >> > > > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "Google App Engine" group. > > > To unsubscribe from this group and stop receiving emails from it, send an > > > email to google-appengine+unsubscr...@googlegroups.com. > > > To post to this group, send email to google-appengine@googlegroups.com. > > > Visit this group at http://groups.google.com/group/google-appengine?hl=en. > > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Re: Instances still getting killed and causing user 500's
+1 to Mos Trust me; Google has no clue what's going on. The instance scheduler went crazy, people have downtimes and have increased billing (for weeks!) If Google would be able to track the problem (or would have a clue how to fix it), they would give a comment. As I wrote. That's not the first time. Last year we had the same situation for weeks. Google is not learning from past faults. That's the biggest problem. Check the latest comments of last years issue: http://code.google.com/p/googleappengine/issues/detail?id=8004 I think it is important to make this behavior public. And I hope the press will tell the story. All in all GAE is not a priority product of Google and I'm sure that it is out of business in the next five years! On Thu, Feb 28, 2013 at 4:23 AM, Prashant Hegde wrote: > Many apps are hitting the same issue, starring the following may increase > chances of getting resolution. The app engine performance is unpredictable. > Right now, as far as we are concerned, the most effective solution is to > offer prayers very sincerely every morning. > > http://code.google.com/p/googleappengine/issues/detail?id=8781 > > This issue has been around for a few weeks with no resolution or any > semblance of activity. > > Prashant > > > > > > On Thu, Feb 28, 2013 at 7:15 AM, Cesium wrote: >> >> Oh Joy, >> >> Now the console charts have been erased. >> >> I'm losing it. >> >> Unicorn liver pate for dinner. >> >> David >> >> >> >> On Wednesday, February 27, 2013 6:10:37 PM UTC-7, Cesium wrote: >> > Starting about 16:30 Pacific time, my Java HRD Instances were shutting >> > down after just a few seconds. >> > >> > Just as my rage reached class IV, serving returned to normal. >> > >> > I know this is an overreaction, but I may have to sacrifice a unicorn. >> > >> > Please, please, App Engine team, spare Mr. Sparkles. >> > >> > >> > This is disheartening, >> > David >> > >> > On Wednesday, February 27, 2013 11:32:07 AM UTC-7, Chris Tan wrote: >> > > I'm also getting this problem. >> > > >> > > On Wednesday, February 27, 2013 7:50:47 AM UTC-8, Kinesh Patel >> > > wrote:On Python 2.7 paid app. Setting an idle instance seems to mitigate >> > > this, but every time a new dynamic instance is spawned or hit i get this >> > > problem. Definitely not normal behavior. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to google-appengine+unsubscr...@googlegroups.com. >> To post to this group, send email to google-appengine@googlegroups.com. >> Visit this group at http://groups.google.com/group/google-appengine?hl=en . >> For more options, visit https://groups.google.com/groups/opt_out. >> >> > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to google-appengine+unsubscr...@googlegroups.com. > To post to this group, send email to google-appengine@googlegroups.com. > Visit this group at http://groups.google.com/group/google-appengine?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Re: Instances still getting killed and causing user 500's
Trust me; Google has no clue what's going on. The instance scheduler went crazy, people have downtimes and have increased billing (for weeks!) If Google would be able to track the problem (or would have a clue how to fix it), they would give a comment. As I wrote. That's not the first time. Last year we had the same situation for weeks. Google is not learning from past faults. That's the biggest problem. Check the latest comments of last years issue: http://code.google.com/p/googleappengine/issues/detail?id=8004 I think it is important to make this behavior public. And I hope the press will tell the story. All in all GAE is not a priority product of Google and I'm sure that it is out of business in the next five years! On Thu, Feb 28, 2013 at 4:23 AM, Prashant Hegde wrote: > Many apps are hitting the same issue, starring the following may increase > chances of getting resolution. The app engine performance is unpredictable. > Right now, as far as we are concerned, the most effective solution is to > offer prayers very sincerely every morning. > > http://code.google.com/p/googleappengine/issues/detail?id=8781 > > This issue has been around for a few weeks with no resolution or any > semblance of activity. > > Prashant > > > > > > On Thu, Feb 28, 2013 at 7:15 AM, Cesium wrote: >> >> Oh Joy, >> >> Now the console charts have been erased. >> >> I'm losing it. >> >> Unicorn liver pate for dinner. >> >> David >> >> >> >> On Wednesday, February 27, 2013 6:10:37 PM UTC-7, Cesium wrote: >> > Starting about 16:30 Pacific time, my Java HRD Instances were shutting >> > down after just a few seconds. >> > >> > Just as my rage reached class IV, serving returned to normal. >> > >> > I know this is an overreaction, but I may have to sacrifice a unicorn. >> > >> > Please, please, App Engine team, spare Mr. Sparkles. >> > >> > >> > This is disheartening, >> > David >> > >> > On Wednesday, February 27, 2013 11:32:07 AM UTC-7, Chris Tan wrote: >> > > I'm also getting this problem. >> > > >> > > On Wednesday, February 27, 2013 7:50:47 AM UTC-8, Kinesh Patel >> > > wrote:On Python 2.7 paid app. Setting an idle instance seems to mitigate >> > > this, but every time a new dynamic instance is spawned or hit i get this >> > > problem. Definitely not normal behavior. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to google-appengine+unsubscr...@googlegroups.com. >> To post to this group, send email to google-appengine@googlegroups.com. >> Visit this group at http://groups.google.com/group/google-appengine?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to google-appengine+unsubscr...@googlegroups.com. > To post to this group, send email to google-appengine@googlegroups.com. > Visit this group at http://groups.google.com/group/google-appengine?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Re: Instances still getting killed and causing user 500's
Many apps are hitting the same issue, starring the following may increase chances of getting resolution. The app engine performance is unpredictable. Right now, as far as we are concerned, the most effective solution is to offer prayers very sincerely every morning. http://code.google.com/p/googleappengine/issues/detail?id=8781 This issue has been around for a few weeks with no resolution or any semblance of activity. Prashant On Thu, Feb 28, 2013 at 7:15 AM, Cesium wrote: > Oh Joy, > > Now the console charts have been erased. > > I'm losing it. > > Unicorn liver pate for dinner. > > David > > > > On Wednesday, February 27, 2013 6:10:37 PM UTC-7, Cesium wrote: > > Starting about 16:30 Pacific time, my Java HRD Instances were shutting > down after just a few seconds. > > > > Just as my rage reached class IV, serving returned to normal. > > > > I know this is an overreaction, but I may have to sacrifice a unicorn. > > > > Please, please, App Engine team, spare Mr. Sparkles. > > > > > > This is disheartening, > > David > > > > On Wednesday, February 27, 2013 11:32:07 AM UTC-7, Chris Tan wrote: > > > I'm also getting this problem. > > > > > > On Wednesday, February 27, 2013 7:50:47 AM UTC-8, Kinesh Patel > wrote:On Python 2.7 paid app. Setting an idle instance seems to mitigate > this, but every time a new dynamic instance is spawned or hit i get this > problem. Definitely not normal behavior. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to google-appengine+unsubscr...@googlegroups.com. > To post to this group, send email to google-appengine@googlegroups.com. > Visit this group at http://groups.google.com/group/google-appengine?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Instances still getting killed and causing user 500's
A couple hours later, all is well. Instances are lasting. Latency is low. Thank you Mr. Sparkles. (burp). On Wednesday, February 27, 2013 6:45:50 PM UTC-7, Cesium wrote: > Oh Joy, > > Now the console charts have been erased. > > I'm losing it. > > Unicorn liver pate for dinner. > > David > > > > On Wednesday, February 27, 2013 6:10:37 PM UTC-7, Cesium wrote: > > Starting about 16:30 Pacific time, my Java HRD Instances were shutting down > > after just a few seconds. > > > > Just as my rage reached class IV, serving returned to normal. > > > > I know this is an overreaction, but I may have to sacrifice a unicorn. > > > > Please, please, App Engine team, spare Mr. Sparkles. > > > > > > This is disheartening, > > David > > > > On Wednesday, February 27, 2013 11:32:07 AM UTC-7, Chris Tan wrote: > > > I'm also getting this problem. > > > > > > On Wednesday, February 27, 2013 7:50:47 AM UTC-8, Kinesh Patel wrote:On > > > Python 2.7 paid app. Setting an idle instance seems to mitigate this, but > > > every time a new dynamic instance is spawned or hit i get this problem. > > > Definitely not normal behavior. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Instances still getting killed and causing user 500's
Oh Joy, Now the console charts have been erased. I'm losing it. Unicorn liver pate for dinner. David On Wednesday, February 27, 2013 6:10:37 PM UTC-7, Cesium wrote: > Starting about 16:30 Pacific time, my Java HRD Instances were shutting down > after just a few seconds. > > Just as my rage reached class IV, serving returned to normal. > > I know this is an overreaction, but I may have to sacrifice a unicorn. > > Please, please, App Engine team, spare Mr. Sparkles. > > > This is disheartening, > David > > On Wednesday, February 27, 2013 11:32:07 AM UTC-7, Chris Tan wrote: > > I'm also getting this problem. > > > > On Wednesday, February 27, 2013 7:50:47 AM UTC-8, Kinesh Patel wrote:On > > Python 2.7 paid app. Setting an idle instance seems to mitigate this, but > > every time a new dynamic instance is spawned or hit i get this problem. > > Definitely not normal behavior. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Instances still getting killed and causing user 500's
Starting about 16:30 Pacific time, my Java HRD Instances were shutting down after just a few seconds. Just as my rage reached class IV, serving returned to normal. I know this is an overreaction, but I may have to sacrifice a unicorn. Please, please, App Engine team, spare Mr. Sparkles. This is disheartening, David On Wednesday, February 27, 2013 11:32:07 AM UTC-7, Chris Tan wrote: > I'm also getting this problem. > > On Wednesday, February 27, 2013 7:50:47 AM UTC-8, Kinesh Patel wrote:On > Python 2.7 paid app. Setting an idle instance seems to mitigate this, but > every time a new dynamic instance is spawned or hit i get this problem. > Definitely not normal behavior. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Instances still getting killed and causing user 500's
I'm also getting this problem. On Wednesday, February 27, 2013 7:50:47 AM UTC-8, Kinesh Patel wrote: > > On Python 2.7 paid app. Setting an idle instance seems to mitigate this, > but every time a new dynamic instance is spawned or hit i get this problem. > Definitely not normal behavior. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
