It was actually pretty automatic - but I didn't have any data (I wasn't 
using a datastore at all)...so it was more an effort of just building and 
uploading to a different application.  The biggest issue we had was getting 
billing set up (not a google/appengine issue - a company accounting process 
issue).

-Nathan

On Tuesday, March 20, 2012 1:02:21 AM UTC-6, Dennis wrote:
>
> I'm planning to do the same (migrate to HRD), but now my expectation have 
> been lowered...
>
> Any tips on doing the migration??  The docs make it look pretty automatic, 
> but it sounds like you spent a more realistic amount of time doing the 
> migration....
>
> Dennis
>
>
>
> On Tuesday, March 20, 2012 2:28:00 AM UTC+8, toonetown wrote:
>>
>> So - spent the weekend and this morning migrating to HRD...took all of 12 
>> minutes before I started getting the same HardDeadlineExceeded exceptions. 
>> :(
>>
>> BOOOOOO!
>>
>> -Nathan
>>
>> On Thursday, March 15, 2012 5:49:02 PM UTC-6, Jeff Schnitzer wrote:
>>>
>>> On Thu, Mar 15, 2012 at 7:36 PM, toonetown <nathan.to...@gmail.com> 
>>> wrote:
>>> > So, explain this to me...is this only a master/slave issue, and those 
>>> with high replication data store aren't seeing the harddeadlinexceeded 
>>> exceptions? That wouldn't make sense in our case, as we use absolutely no 
>>> data store functionality.
>>> >
>>> > I'd be willing to migrate my app if it would make any difference...but 
>>> I can't see how it would be any different.
>>>
>>> The difference is that Google actually cares about uptime on the HRD.
>>>
>>> Jeff
>>>
>>>

-- 
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/-/K4ByWt9mBnAJ.
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.

Reply via email to