[google-appengine] Re: Old versions still running (flexible environment)

The proper way to get due attention for your issue is to register it in the Public Issue Tracker . All useful information should be there, such as project ID, version number, programming language, and output of the gcloud info command. To keep details such as p

Re: [google-appengine] Re: Old versions still running (flexible environment)

Hi Daniel, I use automatic scaling with 1 max-instances in my dev project. This is one thing that helps to limit the costs of the dev environment. I also debug and test the app locally first, before I deploy anything to GAE. In your case with Node.js flex:

[google-appengine] Re: Old versions still running (flexible environment)

I found myself in the same situation. A couples months ago we were going through heavy *development / deploying / testing* and got ourselves with a *huge* bill. Do you confirm that using automatic scaling and setting it to 1 max-instances will fix it? Thanks in advance. El sábado, 18 de marzo

[google-appengine] Re: Old versions still running (flexible environment)

Seeing this in standard env on python as well. Traffic alloc is set to 100%, but last 2 versions (which are several days old) are still running 3 or 4 instances. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this gr

[google-appengine] Re: Old versions still running (flexible environment)

Yep, this is really easy do reproduce in the standard env as well. Just deploy a new version, migrate traffic to the new version. The old version still keeps instances running (in my case both python and java). Den måndag 26 februari 2018 kl. 15:49:58 UTC+1 skrev Hendrik Kleinwächter: > > We ar

[google-appengine] Re: Old versions still running (flexible environment)

We are seeing this as well. Using ruby and the flexible environment. Any idea what this could be? Are the stale instances still producing costs? On Thursday, March 16, 2017 at 8:10:07 PM UTC+1, Alan deLespinasse wrote: > > I'm not sure if this is a bug or expected behavior. It's not what I > exp

[google-appengine] Re: Old versions still running (flexible environment)

We're also seeing this On Friday, 17 March 2017 06:10:07 UTC+11, 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

[google-appengine] Re: Old versions still running (flexible environment)

Flexible, Node.js 6.9.3 or something. On Sunday, July 16, 2017 at 4:04:17 AM UTC-4, Matthew Kime wrote: > > Which version of app engine are you using? We're using the flex > environment with custom runtime. > > thanks, > matt > -- You received this message because you are subscribed to the Goog

[google-appengine] Re: Old versions still running (flexible environment)

Which version of app engine are you using? We're using the flex environment with custom runtime. thanks, matt -- 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

[google-appengine] Re: Old versions still running (flexible environment)

I did have one case a couple weeks ago where an old version was unexpectedly still running. So I guess it's not 100% fixed on Google's side, although that was the only time I've seen it since January. On Friday, July 14, 2017 at 6:57:00 PM UTC-4, Matthew Kime wrote: > > Have your problems been f

[google-appengine] Re: Old versions still running (flexible environment)

Have your problems been fixed? I'm still seeing them. On Monday, March 20, 2017 at 11:35:08 AM UTC-5, Alan deLespinasse wrote: > > Thanks! I'll wait and see if it happens again. > > On Monday, March 20, 2017 at 12:28:04 PM UTC-4, Zachary Fewtrell wrote: >> >> Hi Alan, >> Generally we would expect

[google-appengine] Re: Old versions still running (flexible environment)

Thanks! I'll wait and see if it happens again. On Monday, March 20, 2017 at 12:28:04 PM UTC-4, Zachary Fewtrell wrote: > > Hi Alan, > Generally we would expect a failed deployment to rollback (i.e. delete > the new version & leave the old one running). However your example is from > January an

[google-appengine] Re: Old versions still running (flexible environment)

Hi Alan, Generally we would expect a failed deployment to rollback (i.e. delete the new version & leave the old one running). However your example is from January and some rollback related issues have been addressed since then. If you are still getting the issue I recommend you file an issue

[google-appengine] Re: Old versions still running (flexible environment)

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

[google-appengine] Re: Old versions still running (flexible environment)

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 until you manually shut them down. O