[google-appengine] Re: Migrating from MS to HR
I'm curious how this works for you. When I did this I could not disable my old Google Apps app.. I had to remove the URL, create a new app in my Google apps and set it's URL... What I am saying is that for me I CANNOT delete an old app engine app from my Google apps account. I am curious if the feature works for anyone else. To clarify, I do not mean I can't disable/delete an app engine app, I mean within my Google Apps Dashboard I cannot remove an app I added for my domain. On Apr 1, 11:54 pm, "Brandon Wirtz" wrote: > In google apps for domains you undeploy A1.appspot.com and deploy > b2.appsopt.com > > It's not switch, it's "blow away" and put in the new. > > And you may want to practice first, and do it on a weekday, cause we've had > trouble with apps for domains not letting us create a new subdomain at > times, and we've had trouble with it saying a domain was in use after > deleting it. > > So really, you should upgrade to the Apps For Domains for Business... Have > your pin, and do it with a CSR on the phone. > > > > > > > > -Original Message- > From: google-appengine@googlegroups.com > > [mailto:google-appengine@googlegroups.com] On Behalf Of Greg > Sent: Friday, April 01, 2011 8:55 PM > To: Google App Engine > Subject: [google-appengine] Migrating from MS to HR > > I have a production appengine app atwww.example.com, which I want to switch > from master-slave to high replication datastore. I intend to document and > publish the process and the results to make switching easier for others who > want to make the move. > > The cut-over must be as seamless as possible. I can set up the HR app and > transfer most of the data across ahead of time using the appspot URL, > followed by testing the new app to make sure everything works as expected. > Then there will have to be a small downtime window while I disable the old > app and transfer the remaining data. > > My questions (so far!) are: > > 1. What is the process for switching old to new app in google apps? > Currently in my example.com google apps dashboard I have a link to disable > the old app. When I do this, will I will get the option to associate the new > app with the domain? > > 2. How quick can this app switch happen? Is there any manual component on > Google's end that would require me to do this in office hours? > > -- > 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-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group > athttp://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 google-appengine@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.
[google-appengine] Re: Migrating from MS to HR
On Apr 3, 11:51 am, JH wrote: > I'm curious how this works for you. When I did this I could not > disable my old Google Apps app.. I had to remove the URL, create a new > app in my Google apps and set it's URL... Thanks for your report, JH. I'm pretty sure you're correct - you have two apps (the old MS one and the new HR one), and you disable the MS one in google apps dashboard, then add the new one. I now believe you add the new one by setting the URL in appengine dashboard, and then authorise it in google apps dashboard. Brandon's comments about problems switching the URL are a BIG concern. It not only adds huge uncertainty to the migration process, but makes it seem like it has to be done during office hours (so a CSR is available). Given the data transfer is likely to take a noticable amount of time, for a production app, this is highly undesirable JH, did you have any problems here? How long was it between removing the URL and adding it again in the new app? And Googlers, some reassurance on this point would be good. -- 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-appengine@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.
[google-appengine] Re: migrating from ms to hr: Re-parenting, root entities and performance
Hi Kenneth, There are a few good articles about writing scalable applications for google app engine: http://code.google.com/appengine/articles/scaling/overview.html An example that might help: http://code.google.com/appengine/articles/sharding_counters.html - Wen On Aug 5, 7:51 am, Kenneth wrote: > There's a lot of good information bubbling out about the pitfalls of moving > from from ms to hr, especially the problems with keys having your appid in > them. Apologies if this question has come up before. > > Like most others I suspect, 99% of my datastore objects don't have parents. > Since these are all in the same root entity group I'm now limited to 1-10 > writes per second to all of these objects if I don't reparent, according > tohttp://code.google.com/appengine/docs/python/datastore/hr/overview.ht... > > If my write rate does climb above 10/s I assume that I'm going to block? > > What is the strategy here? I can see making up something random as the > parent, but then I need that random thing to do a get_by_id since that's > what I do in most of my app, only passing the id to the user rather than the > whole key (which you are not supposed to pass to the user because it is a > security issue if you're using namespace). Am I screwed? > > This is of course leaving the whole issue of consistency aside, I'm ok with > that side of things, more or less. > > Thanks. -- 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-appengine@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.
Re: [google-appengine] Re: migrating from ms to hr: Re-parenting, root entities and performance
Hello, Yes, this limit applies to entity groups. 1. Entity Kind != entity group 2. "No entity group parent" means an entity is its own entity group root The pitfalls here revolve around consistency guarantees. Check out these slides I did that describe the differences in consistency guarantees: http://www.slideshare.net/ikailan/2011-julygtughighreplicationdatastore -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Fri, Aug 5, 2011 at 2:06 PM, App Engine Group wrote: > Hi Kenneth, > > There are a few good articles about writing scalable applications for > google app engine: > http://code.google.com/appengine/articles/scaling/overview.html > > An example that might help: > http://code.google.com/appengine/articles/sharding_counters.html > > - Wen > > > On Aug 5, 7:51 am, Kenneth wrote: > > There's a lot of good information bubbling out about the pitfalls of > moving > > from from ms to hr, especially the problems with keys having your appid > in > > them. Apologies if this question has come up before. > > > > Like most others I suspect, 99% of my datastore objects don't have > parents. > > Since these are all in the same root entity group I'm now limited to 1-10 > > writes per second to all of these objects if I don't reparent, according > tohttp://code.google.com/appengine/docs/python/datastore/hr/overview.ht... > > > > If my write rate does climb above 10/s I assume that I'm going to block? > > > > What is the strategy here? I can see making up something random as the > > parent, but then I need that random thing to do a get_by_id since that's > > what I do in most of my app, only passing the id to the user rather than > the > > whole key (which you are not supposed to pass to the user because it is a > > security issue if you're using namespace). Am I screwed? > > > > This is of course leaving the whole issue of consistency aside, I'm ok > with > > that side of things, more or less. > > > > Thanks. > > -- > 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-appengine@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. > > -- 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-appengine@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.
