OceanCron: does not run until a request has been made
Issue #289
wontfix
Despite setting min_idle_instances and min_instances to 1, OceanCron does not appear to run until one request has been made.
Comments (3)
-
-
reporter It would seem that not automatically restarting a re-deployed app that has the same version is a “feature” of App Engine Standard Edition.
Only when a new version is deployed is the app automatically restarted.
With Flex Edition, you can force a restart with the following command after deploying:
gcloud app instances restart <project-id>
There is no such option for Standard Edition, though.
Of course, hitting the home page has exactly the same effect :-)
-
reporter - changed status to wontfix
As noted, this is a feature of GAE Standard Edition.
- Log in to comment
I tested this with a re-deploy:
11:00 - Set a cron to execute at 11:20
11:05 - I re-deployed OceanCron
11:07 - Build finished with logs:
11:08 - session was shutdown for some reason:
11:20 - The cron did not run.
11:22 - Loaded OceanCron homepage in my browser, it took roughly 25 seconds to load. The logs were as follows:
In summary this test confirmed that no instance is running after OceanCron is deployed until the first request is made.