Hi: I got and index built incorrectly and I tried to rebuild it by iterating the entities reading and putting them back, despite it added many lost entities to the index some were still missed.
Finally I decided to delete all the entities of the kind to import them back from scratch. I used a queue to delete 100 entities per task and after finishing the task enqueuing a new task. At certain point it started to raise db.Timeout exceptions, the queue as expected retries the task because the http status it's not 200. Then it was all the time trying to delete 100 entities but raising a db.Timeout exception consuming lot of CPU despite no entity was erased. After some hours ( there were like 90k entities ) all my free cpu time was gone, getting the overquota error and there were still entities left. I think that if it raises a db.Timeout it shouldn't decrease the cpu time available. I solved the problem, removing 50 entities at a time and adding a delay each time a db.Timeout raised. What I mean after this little tale is that it would be nice to have an easy way to truncate a kind ( Not that easy that you can remove it by accident hehehe ). Cheers, JP -- 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.
