HRD migration / Severe Datastore admin failure
40 views
Skip to first unread message
Marcel Manz
Nov 20, 2011, 6:41:29 AM11/20/11
to google-a...@googlegroups.com
I was migrating one of my Java MS apps to HRD using the migration tool. So far so good. After having copied, tested and applied the switch to the HRD app, all went fine so far.
Then however the horror starts to begin:
1. Instead of just disable billing and leave my MS app in some kind of over-quota state (is has more than the free limits stored), I decided to be nice and clean-out the datastore in the MS app before I disable the billing (I didn't want to delete my MS app right away and leave it at least for some additional days in case something happens).
2. So I reactivated datastore writes on my MS app (it was set read-only after performing the HRD migration), and used the Datastore Admin to bulk-delete my MS entities.
3. Having clearly verified that I'm on my old MS app, I hit 'Delete entities' and the Datastore Admin began its job. #BIG FAILURE!
After its completion, I sadly had to see that the Datastore Admin DID NOT delete the entities from my upper-left visible MS app, but from the newly migrated HRD app. WTF!
Hitting 'Datastore Viewer' in the HRD app showed an empty datastore. Going back to my MS app, opening the Datastore Admin just shows 1 kind (even there are two visible in the Datastore viewer). Hitting 'Copy' outputs a warning that the source application would be configured to use HR Datastore.
Now it's pretty obvious what happened: the Datastore Admin in my old MS app took orders to be executed in my migrated HRD app !!
The Data in my old MS app is still present, however as the migration tool completed I'm unable to restart the copy process. I would like to have this data re-transferred to my HRD app. Please contact me offlist for corresponding app id's. Fortunately for me, it's only log-data and my app doesn't rely on it. Still, something like this should not happen in the first place or App Engine should prevent the standard actions I've performed after migrating to HRD. It was nowhere clear that the Datastore Admin is going to delete my HRD data, while I was setting up the delete job on the MS version.
Thanks
Marcel
Then however the horror starts to begin:
1. Instead of just disable billing and leave my MS app in some kind of over-quota state (is has more than the free limits stored), I decided to be nice and clean-out the datastore in the MS app before I disable the billing (I didn't want to delete my MS app right away and leave it at least for some additional days in case something happens).
2. So I reactivated datastore writes on my MS app (it was set read-only after performing the HRD migration), and used the Datastore Admin to bulk-delete my MS entities.
3. Having clearly verified that I'm on my old MS app, I hit 'Delete entities' and the Datastore Admin began its job. #BIG FAILURE!
After its completion, I sadly had to see that the Datastore Admin DID NOT delete the entities from my upper-left visible MS app, but from the newly migrated HRD app. WTF!
Hitting 'Datastore Viewer' in the HRD app showed an empty datastore. Going back to my MS app, opening the Datastore Admin just shows 1 kind (even there are two visible in the Datastore viewer). Hitting 'Copy' outputs a warning that the source application would be configured to use HR Datastore.
Now it's pretty obvious what happened: the Datastore Admin in my old MS app took orders to be executed in my migrated HRD app !!
The Data in my old MS app is still present, however as the migration tool completed I'm unable to restart the copy process. I would like to have this data re-transferred to my HRD app. Please contact me offlist for corresponding app id's. Fortunately for me, it's only log-data and my app doesn't rely on it. Still, something like this should not happen in the first place or App Engine should prevent the standard actions I've performed after migrating to HRD. It was nowhere clear that the Datastore Admin is going to delete my HRD data, while I was setting up the delete job on the MS version.
Thanks
Marcel
Joshua Smith
Nov 20, 2011, 8:29:35 AM11/20/11
to google-a...@googlegroups.com
Yikes!
Lesson: After migration, disable billing on the M/S app, disable the M/S app. Don't delete anything.
--
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/-/WOxr_EEzXOYJ.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Reply all
Reply to author
Forward
0 new messages