Note that there are some explanatory texts on larger screens.

plurals
  1. POGAE Can't set up a Resident Instance, related to new Migrate Settings option?
    primarykey
    data
    text
    <p>I am trying to create a couple of resident instances on a google app engine app hosted on appspot.com. I moved the idle instances slider from Auto down to 2. My understanding is that this will then create two "resident" instances and I should see those marked as Resident instead of Dynamic in the instances screen. But it isn't working, I am still only seeing 1 dynamic instance (this is a test with no traffic).</p> <p>When I made and saved the idle instances change, I noticed what to me was a new option underneath that section, as follow :</p> <blockquote> <p>Performance Settings Migration for Modules</p> <p>Before you can modify performance settings across Modules, your settings must be migrated. After the migration, performance settings will be managed at the Module level, and changes must be made through your app.yaml (Python) or appengine-web.xml (Java). Copy the settings clause below to the appropriate file to preserve your performance settings during the next update.</p> </blockquote> <p>There is a button under this new section called Migrate Settings. When I click this the main screen just blanks, with the admin console menu options still available on the side. All very peculiar! </p> <p>It also gives some setting for python and java to do the idle instances down to 2 change at the module config level. I stuck this into my appengine-web.xml and re-deployed but I am still only getting one dynamic instance.</p> <p>Has anyone any experience of this "migrate settings" option? </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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