4 ms·

FYI, the Python 2.7 runtime is only supported for apps using the High Replication Datastore. This is important to note for any 'older' apps that were created b

FYI, the Python 2.7 runtime is only supported for apps using the High Replication Datastore. This is important to note for any 'older' apps that were created before HRD was enabled. http://code.google.com/appengine/docs/python/datastore/hr/#Selecting_a_Datastore http://code.google.com/appengine/docs/python/datastore/hr/#S...

endlessvoid94 15y ago
I can totally appreciate the fact that they've kicked it in the ass to get python 2.7 working for concurrent requests, in light of their recent pricing changes. But I have an old app (thathigh.com) that does not use the high replication datastore. I never transitioned it, because quite frankly it wasn't worth the effort. Now I have to do three things: move from django 0.96 to 1.2 (no small feat), bring my app down in order to migrate everything to high replication datastore, and then ensure all my queries work like they did before. That's not a small amount of work, especially since it's a side project.
- wildermj 15y ago
  There are a lot more advantages to moving your app to HRD, like no more random datastore timeouts. There is also a new migration in limited testing right now that will allow you to migrate your data in multiple passes, which will minimize the read-only time required for your app to migrate.
- mshafrir 15y ago
  I just migrated an app. I had to make a few updates to app.yaml, remove use_library() references in the code, create a new config file that permits the old app to write to the new app, disable billing on the old app and enable it on the new one (will take a few days for this to resolve), disable writes on the old app, switch over my Google Domain config to point to the new app, and a few other things I'm forgetting. Not as bad as I thought it would be, but still non-trivial and this was for a relatively simple app. If you're considering making the switch, take a look at http://code.google.com/appengine/docs/adminconsole/datastoreadmin.html#Copying_Entities_to_Another_Application http://code.google.com/appengine/docs/adminconsole/datastore...

endlessvoid94 15y ago

I can totally appreciate the fact that they've kicked it in the ass to get python 2.7 working for concurrent requests, in light of their recent pricing changes. But I have an old app (thathigh.com) that does not use the high replication datastore. I never transitioned it, because quite frankly it wasn't worth the effort. Now I have to do three things: move from django 0.96 to 1.2 (no small feat), bring my app down in order to migrate everything to high replication datastore, and then ensure all my queries work like they did before. That's not a small amount of work, especially since it's a side project.

wildermj 15y ago
There are a lot more advantages to moving your app to HRD, like no more random datastore timeouts. There is also a new migration in limited testing right now that will allow you to migrate your data in multiple passes, which will minimize the read-only time required for your app to migrate.
mshafrir 15y ago
I just migrated an app. I had to make a few updates to app.yaml, remove use_library() references in the code, create a new config file that permits the old app to write to the new app, disable billing on the old app and enable it on the new one (will take a few days for this to resolve), disable writes on the old app, switch over my Google Domain config to point to the new app, and a few other things I'm forgetting. Not as bad as I thought it would be, but still non-trivial and this was for a relatively simple app. If you're considering making the switch, take a look at http://code.google.com/appengine/docs/adminconsole/datastoreadmin.html#Copying_Entities_to_Another_Application http://code.google.com/appengine/docs/adminconsole/datastore...