8

My app is running on App engine Java SDK, and since this morning I noticed that open instances are not handling new requests, and instead, new Frontent instances are being started. So now i have about 250 open instances (a lot more than usual). Also, the instances are running on version 1.9.5.

Please advice!

Andrei F
  • 4,205
  • 9
  • 35
  • 66
  • 1
    I'm seeing this too! Since this morning - we [greatly] ran over our daily budget in a few hours – MeLight May 09 '14 at 08:03
  • 2
    please star this bug: https://code.google.com/p/googleappengine/issues/detail?id=10894&sort=-opened&colspec=ID%20Type%20Component%20Status%20Stars%20Summary%20Language%20Priority%20Owner%20Log%20Opened – Jens May 09 '14 at 08:57
  • Having the same problem. Each request starts a new instance. Ran out f budget right now – Zensursula May 09 '14 at 14:23

2 Answers2

12

The issue has been fixed by Google at 2014-05-09 10:15 (US Pacific Time). See Google App Engine Downtime Notify

How we fixed the issue temporarily: Disable and re-enable the application inside the Application Settings. After doing this everything went back to normal. Since then we only saw instances spawning with the version 1.9.4. In our case a lot of instances spawned again after 45 minutes.

To make sure you won't get billed choose a maximum of Idle Instances inside the Application Settings. We changed the maximum to 4 idle instances. In this case a lot of instances still stick around, but you don't get billed.

Our App Engine instances graph: App Engine instances graph

Nik Graf
  • 3,469
  • 2
  • 16
  • 23
  • 1
    Strange thing: for my app, although there are over 350 instances started, the Billed line is normal. (2-3 instances billed) - maybe this is because we already had a maxi number of idle instances set. Also, all my instances are now running on v 1.9.4 – Andrei F May 09 '14 at 13:59
  • After you disabled/re-enabled the app, the instance scheduler worked fine ? Did it stopped creating instances for almost every new request ? – Andrei F May 09 '14 at 14:02
  • We just did the same & I updated the answer. Thanks for the hint. – Nik Graf May 09 '14 at 14:10
3

A workaround is: "Disable and re-enable the application inside the Application Settings" https://code.google.com/p/googleappengine/issues/detail?id=10893#c3

mdb
  • 41
  • 2