I don't know if this helps any, but I can see that for every entity type, the last shard seems stuck.
So, if entity X has 1 shard assigned to it, then the details will say that shard 0 is running, the last work item is unknown, and 1 second has elapsed. If entity Y has 26 shards assigned to it, then 0-24 will report success and 25 will be running with 1 second elapsed and an unknown current item. Its like this for every entity kind. On Jun 15, 5:21 pm, tempy <[email protected]> wrote: > I'm trying to migrate to the HR datastore and have started the > process, but with only about 15 MB worth of data it has already gone > through 18 hours of CPU and does not seem to be anywhere near > stopping. This doesn't smell right so I stopped it by pausing the > default queue. > > The status does not change from "Active (0 steps completed, 12 > active)". So, with the default queue paused, I'm not quite sure what > to do. If I start it again it will soon chew through my remaining > quota and bring my app down, but as long as its paused my app isn't > working right anyway. If I purge the queue, are there any steps I > need to take to restart the process? Or maybe its supposed to take > this much time? > > AppID: openkleio -- 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.
