Hi Nick One thing you can do to cut down on re-deploying time is deploy multiple versions of the same code base. ie 1-1-a 1-1-b and 1-1-c
Make one default, if you get a stuck instance, test one of the other versions, if it comes up then make this the default. This can be done in the dashboard or via appcfg. This is much quicker than re-deploying. T On Sep 2, 7:24 pm, Nick Winter <livel...@gmail.com> wrote: > We are seeing the same thing, which we are very familiar with by this > point. App id: skrit > > We get long runs of it, which we can sometimes fix temporarily by > redeploying and restarting all instances. Too bad recently for that to > work. Most recently, things have been bad starting since 8/30 at > 10:23pm PDT, with no lasting respite despite redeploys. > > On Sep 2, 3:10 am, "Wesley C (Google)" <wesc+...@google.com> wrote: > > > > > > > > > are you both still experiencing this problem? > > > when did it start occurring (as close as possible to the real time)? > > > has it stopped yet? if so, also tell us when this problem ended. > > > finally can you both send us all your app IDs? > > > thanks! > > -- wesley > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > "Core Python Programming", Prentice Hall, (c)2007,2001 > > "Python Fundamentals", Prentice Hall, (c)2009 > > http://corepython.com > > > wesley.chun : wesc+api at google.com : @wescpy > > developer relations :: google app engine > > @app_engine :: googleappengine.blogspot.com -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
