On Friday, August 9, 2013 12:27:39 PM UTC-5, aloo wrote: > So new versions of the app spin up new instances? Existing instances don't > get the newly deployed code? >
I wouldn't say "new versions spin up new instances," that leads to confusion about what's happening. The more correct way to say it is "different app versions get their own instances." Remember that App Engine doesn't know which version is new or old (the version doesn't have to be a number, it can be a word too!). All it knows is that you have different versions of the app uploaded, and that you want to run them. So it allocates instances to run each version. By using Traffic Splitting, you can slowly move traffic from one version to another, and that sends a hint to the scheduler: "hey, this version is getting less traffic, maybe I should spool down the instances running that version. But wait, this other version over here is getting more traffic, so I'll allocate more instances to that." If you want to directly replace a version of your app, then upload your application with the same version as the currently deployed default app. ----------------- -Vinny P Technology & Media Advisor Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- 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 http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
