problems usually come before new release

[Peter Ondruška]

Maybe you noticed and maybe it is just rare coincidence but problems we see usually come before new release(?) Is it only me to observed this?

[Barry Hunter]

Surely this is to be expected. 

Before Google annonnces a new release, it has to be rolled out to all servers. So that when the annoncement is made, the new features can actully be used. 

So that means every single server has to be updated. Which almost certainly means bringing it offline (even for jsut a few seconds) - which means all instances running on it, have to be shutdown. 

They probably dont do single servers at a time, but a whole rack/data-center worth. So while a large number of applications are shifted to a new set of servers, there will be a blip. 

(In fact its explicitly noted the rollout is incremental. If they did a system wide restart, not only would it be an intensive process, doing it incrementally means it can be aborted early should issues be found, before it affects all applications) 

Basically every release brings a mass migration, when all applications must be reinitialized on the new system. 

(and that is aside from any bugs, or incompatibltities (intentional or otherwise) that a new version may bring) 

On Wed, Mar 13, 2013 at 8:55 AM, Peter Ondruška <peter.o...@kaibo.eu> wrote:

Maybe you noticed and maybe it is just rare coincidence but problems we see usually come before new release(?) Is it only me to observed this?

--
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-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Peter Ondruška]

OK but I prefer being notified about service disruption beforehand and not afterwards... ;-) in case upgrade _has_ to be done the way it is done.