Hi Alejandro, Yes, definitely. You are 100% right here. I honestly got confused with the backends question and went back to the old "backends" mentality, where the instance was simply UP. Now, if it's not the default one, you are right, App Engine won't keep on spinning them up.
Completely sorry for the wrong message there. I just quickly tested to make sure this is the correct behavior, and the non-default module doesn't kick up instances if there is no traffic. Now if there is traffic, it will obviously change, but that is a whole other story. Cheers! On Wednesday, October 21, 2015 at 5:06:33 AM UTC-4, Alejandro Gonzalez wrote: > > Hello, > > Reading the modules documentation i found a phrase that confuses me... > > min-idle-instances: >> The minimum number of idle instances that App Engine should maintain for >> this version. Only applies to the default version of a module, since other >> versions are not expected to receive significant traffic. > > > > So... > > 1. I have a module version configured with min-idle-instances = 2 (2 > resident instances) > 2. This version is not the default version for the module > 3. This version is not receiving any request > > The 2 min-idle-instances will still apply to this "non default" module > version? If i shutdown the 2 resident instances for that module version... > they are going start again? (please note that i don't have a ready to > deploy project with modules thus i can't test this by myself) > > > Thanks. > > > Thanks again. > > > > > El martes, 20 de octubre de 2015, 18:22:42 (UTC+2), Patrice (Cloud > Platform Support) escribió: >> >> Very welcome :). >> >> I forgot to tell you that, if you believe this is a Feature that could >> potentially benefit a lot of users, you are more than welcome to post it >> here <https://code.google.com/p/googleappengine/issues/list> as a >> Feature Request so we can look into adding that behavior to the console. >> >> Cheers! >> >> On Tuesday, October 20, 2015 at 12:17:03 PM UTC-4, Alejandro Gonzalez >> wrote: >>> >>> Thanks for your clarification Patrice. >>> >>> >>> El martes, 20 de octubre de 2015, 18:13:26 (UTC+2), Patrice (Cloud >>> Platform Support) escribió: >>>> >>>> Hi Alejandro, >>>> >>>> Unfortunately, for your second question, no it cannot be done. From the >>>> console you can only delete a version, not suspend it, so you won't be >>>> able >>>> to deactivate a version, short of completely removing it. You can upload >>>> the same application, but with a different app.yaml, so the instances >>>> aren't up, but you won't be able to "suspend" the version from the console. >>>> >>>> Cheers >>>> >>>> On Tuesday, October 20, 2015 at 12:07:57 PM UTC-4, Christian F. Howes >>>> wrote: >>>>> >>>>> bummer. I don't have an answer for you - the last of my backends were >>>>> deleted a couple of months ago. >>>>> >>>>> I hear you on how changes cascade! >>>>> >>>>> christian >>>>> >>>>> On 10/20/15 02:11, Alejandro Gonzalez wrote: >>>>> > I know backends are deprecated... forget about them (thinking in the >>>>> > refactor i need to made and how it will affect to my CI flow, build >>>>> scripts >>>>> > and app versioning approach...) >>>>> > >>>>> > If I have a module deployed to a version (v1-2-54-back) and >>>>> configured to >>>>> > have 2 resident instances: can i stop that module version from the >>>>> admin >>>>> > console so it does not start more instances (without deleting it so >>>>> i can >>>>> > re-activate it)? >>>>> > >>>>> > Maybe i need to rethink my versioning and deployment processes a >>>>> bit... i >>>>> > will start another specific thread for this if i need advice (I bet >>>>> i will >>>>> > :D) >>>>> > >>>>> > >>>>> > El martes, 20 de octubre de 2015, 1:35:10 (UTC+2), Christian F. >>>>> Howes >>>>> > escribió: >>>>> >> >>>>> >> note that i was reminded by google support recently that backends >>>>> are a >>>>> >> deprecated feature, so i bet managing them in the new console won't >>>>> ever >>>>> >> come. :( >>>>> >> >>>>> >> the modules with manual scaling ("B1" etc. instance classes) work >>>>> great, >>>>> >> and we have found them much easier to manage (the logs are >>>>> separated from >>>>> >> other modules, the deployments are much smoother for us). >>>>> >> >>>>> >> Good luck! >>>>> >> >>>>> >> Christian >>>>> >> >>>>> >> On Monday, October 19, 2015 at 2:49:21 AM UTC-7, Alejandro Gonzalez >>>>> wrote: >>>>> >>> >>>>> >>> Hello, >>>>> >>> >>>>> >>> I have an application that still uses backends instead of modules. >>>>> In the >>>>> >>> new Admin Console there is no section for backends, therefore >>>>> there is a >>>>> >>> feature that i can't use: stop a backend. >>>>> >>> >>>>> >>> Stop a backend means that that backend version stops starting >>>>> instances >>>>> >>> and this is very important when the backend is configured to have >>>>> 2 >>>>> >>> resident instances and you use an incremental version number >>>>> approach when >>>>> >>> deploying backends. >>>>> >>> >>>>> >>> In the new console is there a feature to prevent a version create >>>>> new >>>>> >>> instances? >>>>> >>> >>>>> >>> Thanks. >>>>> >>> >>>>> >>> >>>>> > >>>>> >>>> -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/48fbdfd7-f3aa-4bac-a035-c7d71f63a692%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
