Databases
StackOverflow2013
Postsdbo
POGoogle App Engine Instances keep quickly shutting down
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGoogle App Engine Instances keep quickly shutting down
    primarykey
    data
    text
    <p>So I've been using app engine for quite some time now with no issues. I'm aware that if the app hasn't been hit by a visitor for a while then the instance will shut down, and the first visitor to hit the site will have a few second delay while a new instance fires up.</p> <p>However, recently it seems that the instances only stay alive for a very short period of time (sometimes less than a minute), and if I have 1 instance already up and running, and I refresh an app webpage, it still fires up another instance (and the page it starts is minimal homepage HTML, shouldn't require much CPU/memory). Looking at my logs its constantly starting up new instances, which was never the case previously.</p> <p>Any tips on what I should be looking at, or any ideas of why this is happening?</p> <p>Also, I'm using Python 2.7, threadsafe, python_precompiled, warmup inbound services, NDB.</p> <p><strong>Update:</strong></p> <p>So I changed my app to have at least 1 idle instance, hoping that this would solve the problem, but it is still firing up new instances even though one resident instance is already running. So when there is just the 1 resident instance (and I'm not getting any traffic except me), and I go to another page on my app, it is still starting up a new instance. </p> <p>Additionally, I changed the Pending Latency to 1.5s as koma pointed out, but that doesn't seem to be helping. </p> <p>The memory usage of the instances is always around 53MB, which is surprising when the pages being called aren't doing much. I'm using the F1 Frontend Instance Class and that has a limit of 128, but either way 53MB seems high for what it should be doing. Is that an acceptable size when it first starts up?</p> <p><strong>Update 2:</strong> I just noticed in the dashboard that in the last 14 hours, the request /_ah/warmup responded with 24 404 errors. Could this be related? Why would they be responding with a 404 response status?</p> <p><strong>Main question:</strong> Why would it constantly be starting up new instances (even with no traffic)? Especially where there are already existing instances, and why do they shut down so quickly?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USadam
    1. USadam
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POGoogle App Engine Instances keep quickly shutting down
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POGoogle App Engine Instances keep quickly shutting down
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POGoogle App Engine Instances keep quickly shutting down
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWith regard to the /_ah/warmup requests getting 404s, I found my answer here: http://stackoverflow.com/questions/4605228/how-do-i-configure-warming-requests-avoiding-errors-404-on-apps-log
      singulars
      1. POGoogle App Engine Instances keep quickly shutting down
      1. USadam
    2. COgo higher on your min pending latency, just checked and it is set to 2.5 secs - not 1.5 secs - for me; i'm fairly sure that this will prevent starting up too many instances.
      singulars
      1. POGoogle App Engine Instances keep quickly shutting down
      1. USkoma
    3. COand give it 10mins for the setting to propagate
      singulars
      1. POGoogle App Engine Instances keep quickly shutting down
      1. USkoma
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload