We have some services that are manual and some that are automatic. I'm pretty sure both have had this problem.
I wouldn't have interpreted that documentation as saying that manual scaling would keep old *versions* running. Our manual-scaling services are configured to have one *instance*. We've ended up having multiple *versions* running, each with one instance, although all traffic was routed to a single version. And like I said, normally when we deploy a new version, the old version is shut down automatically. It's just when a second version has failed to start up, and we deploy a third version, only the first version is shut down, and the second version still appears to be running, with 0% traffic. The behavior of the gcloud app deploy command in this case is misleading. On Saturday, March 18, 2017 at 12:39:42 PM UTC-4, Adam (Cloud Platform Support) wrote: > > Are you using manual scaling or automatic scaling in your app.yaml? If > you're using manual scaling, App Engine will try to keep instances alive > indefinitely > <https://cloud.google.com/appengine/docs/flexible/nodejs/how-instances-are-managed#instance_uptime> > > until you manually shut them down. > > On Thursday, March 16, 2017 at 3:10:07 PM UTC-4, Alan deLespinasse wrote: >> >> I'm not sure if this is a bug or expected behavior. It's not what I >> expected, but I'm still somewhat confused by the Cloud Console. >> >> I have several services for which I noticed there were still some old >> versions running, although the old versions were serving 0% of traffic. >> Example: >> >> >> <https://lh3.googleusercontent.com/-YZWAxJMW7x4/WMrgCXinq6I/AAAAAAAAMac/iRAXXz_vhjYU9072hPy7ZXGENs4bvoCfQCLcB/s1600/oldservices.png> >> >> The two selected versions were made obsolete by the top version. Normally >> when I deploy a new version, the previously running version is shut down. >> In these cases, I think a new version never succeeded in starting up, >> because I had a bug that would simply crash every time. So here's what >> apparently happens: >> >> 1. Version A is running >> 2. I try to deploy version B; it repeatedly fails to start up. My >> "gcloud app deploy" command eventually returns an error, telling me that >> deployment failed. Version A is still serving all traffic. Version B is >> apparently still running, though I didn't know that until just now. >> 3. I fix the bug and deploy version C. It starts up, version A is >> correctly stopped. Apparently version B is still running, though. >> >> So, is this a bug or expected? Is it costing us money? I'm finding it a >> bit hard to tell what our recent charges are for, although they are a bit >> higher than expected (still looking into that). I'd submit a billing ticket >> if I was sure. >> > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/674f64f8-a717-48ba-aa3b-49849a136595%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
