Instances still getting killed and causing user 500's

[Kinesh Patel]

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.

[Chris Tan]

I'm also getting this problem.

[Cesium]

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

[Cesium]

Oh Joy,

Now the console charts have been erased.

I'm losing it.

Unicorn liver pate for dinner.

David

[Cesium]

A couple hours later, all is well.
Instances are lasting.
Latency is low.

Thank you Mr. Sparkles. (burp).

[Prashant Hegde]

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 

--
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-appengi...@googlegroups.com.
To post to this group, send email to google-a...@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.

[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!

[Thiago Catoto]

+1 to Mos

[Cesium]

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

[Mos]

Hello Takashi,

any feedback for us?

Cheers
Mos

[Michael Hermus]

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.

[johnP]

This morning is a serving train-wreck here, too. 

On Wednesday, February 27, 2013 7:50:47 AM UTC-8, Kinesh Patel wrote:

[Carl Schroeder]

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!

[Cesium]

I'm sure you noticed the question on this forum that Takashi did respond to.

[Cesium]

To paraphrase johnP, "This afternoon is a serving train-wreck."

My poor unicorns' tongues are raw from gorging on Sour Skittles(tm).

David