If you store keys, I believe the migration tools should deal with this case. The issue is if you take the keys and encode them again - we have no way of knowing your encoding scheme.
For 5 gigabytes of data, the downtime should be minimal. Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine On Fri, Jul 8, 2011 at 12:02 PM, Ikai Lan (Google) <[email protected]>wrote: > Yes, we absolutely are building tools to allow self service migrations. > However, there will be downtime. I don't think there is any way around this > unless you are willing to accept data loss (the data that is written to the > M/S app while the migration is happening that is not copied over). > Fortunately, the downtime can be minimized to under a few hours. > > We will not disable applications on master/slave. We just cannot provide an > SLA for master/slave apps. In the long term, we *may* disable the option to > create new master/slave applications. > > Ikai Lan > Developer Programs Engineer, Google App Engine > Blog: http://googleappengine.blogspot.com > Twitter: http://twitter.com/app_engine > Reddit: http://www.reddit.com/r/appengine > > > > On Fri, Jul 8, 2011 at 11:53 AM, Ronoaldo José de Lana Pereira < > [email protected]> wrote: > >> Ikay, >> >> You said "for everyone who deploys using High Replication datastore". Is >> this a hint that the Master/Slave will be discontinued when AppEngine leaves >> preview? >> >> I know that you and the AppEngine team are very busy, but are you planning >> to build tools to help us migrate a live app from MS to HR? My app has >> around 5G of stored data, and is heavily used all day (around 150 reqs/sec), >> so there is almost no room for a downtime migration period if that takes too >> long to complete. Does it takes too long or is there any way to ask for help >> when migrating this so it will be faster? Also, we had the bad idea to store >> the encoded key strings to reference other objects in the datastore. If we >> migrate the app from one appid to another, all those references will break, >> right? Can we do something like migrate the storage but keep the appid? That >> wold be great! >> >> Thanks, >> >> Ronoaldo >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/google-appengine/-/EveQd_kfG40J. >> >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/google-appengine?hl=en. >> > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
