Hi Eric, That's why I can never get rid of those...
Thanks for telling me. I have asked Google to delete them in a separated e-mail. Shinichi On Mon, Mar 15, 2010 at 01:00, Eric Ka Ka Ng <[email protected]> wrote: > Hi Shinichi, > > we can vacuum_indexes for those indexes in 'Serving' state. however, > there are cases that the index being stuck in "Building" state. In > such case, no luck and have to ask people from Google to help to > change the state of those indexes to "Error" and we could then run > vacuum_indexes to remove them > > - eric > > On 15 March 2010 15:06, Shinichi Nakanishi <[email protected]> wrote: >> I didn't even notice there were zombie indexes. >> >> I ran appcfg with vacuum_indexes option. I deleted some zombie >> indexes, but still a lot of indexes which status is "Building". >> >> I have run appcfg vacuum_indexes for several times, but no luck so far. >> >> Can we delete these indexes with status "Building"? >> >> Shinichi >> >> On Sun, Mar 14, 2010 at 20:39, Eric Ka Ka Ng <[email protected]> wrote: >>> Hi, >>> >>> I think you can use the 'vacuum index' command to remove indexes no >>> longer required, then you wont have 'zombie' ;) >>> >>> - eric >>> >>> On 15 March 2010 11:31, Iap <[email protected]> wrote: >>>> Hi, >>>> I will eventually have the same problem because I have many "zombie" >>>> indexes. >>>> These indexes dose not been removed even it was omitted from the >>>> index.yaml. >>>> (The schema of Model has been changing during the developing , >>>> that is the reason why some indexes becomes zombie) >>>> >>>> 2010/3/15 Eric Ka Ka Ng <[email protected]> >>>>> >>>>> Hi Shinichi, >>>>> >>>>> I had exactly the same problem as yours. As far as I know, currently >>>>> billing disabled app has limitation on max. 100 indexes. Billing >>>>> enabled app has limitation on max. 200 indexes. These numbers are not >>>>> billable and there are no ways we could further increase this number >>>>> ,even if the app needs it and we are willing to pay more for the >>>>> required resources. Please correct me if that's not the case anymore >>>>> now. >>>>> >>>> -- >>>> 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. >>>> >>> >>> -- >>> 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. >>> >>> >> >> -- >> 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. >> >> > > -- > 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. > > -- 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.
