On Sun, Oct 12, 2014 at 11:07 PM, Kaan Soral <[email protected]> wrote:
> I hope/assume the scheduler skips the alive/old instances and route > requests to new ones until old requests at hand are completed, however > there is no such(observed) routine for multi-module uploads, would be great > if there was > It sounds like you'd be interested in this issue, in terms of having prewarmed instances available after application uploads: https://code.google.com/p/googleappengine/issues/detail?id=8771 On Sun, Oct 12, 2014 at 11:45 PM, PK <[email protected]> wrote: > A similar issue I have faced is when changing versions of my modules. I > have to do it manually from the app engine console one at a time—at least I > do not know of a better way, is there an API to do this? Many times modules > depend on the same core libraries so I want to “upgrade” all of them > together. If you have several modules by the time you get to the nth module > the first one is already in the new version. > +1. I'd like an API for the Traffic Splitting service to make it easier to move traffic between application versions. And maybe a general API for interacting with App Engine administration (version/module management, instance listing, etc). ----------------- -Vinny P Technology & Media Consultant 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/d/optout.
