Hi, I'm also having the issue of stuck index building. the app is quickbookmarkcom. The indexes have been in the "Building" phase for a couple of days already, and i cannot remove them (vacuum_indexes gives: "indexes were not deleted. Most likely this is because they no longer exist.") I have since changed my app and the indexes are no longer needed.
I would highly appreciate if somebody from Google could have a look at it and remove the indexes that are in the Building phase. Thank you very much, Dejan On May 6, 5:02 pm, Ubaldo Huerta <[email protected]> wrote: > I'm having same issue.Indexbuilding, for a alpha app at this moment > (just 100 entities), and it's stuckbuildingindex. Sounds like one > has to factor in this lag time in the development cycle, that is, > first updateindexdefinitions, wait wait and wait, then upload the > app (well, if one uses versions, can conceivably promote the version > to be the default one whenindexbuildinghas finished ) > > An indication of how many people are ahead in the queue or better yet > (expected duration although I realize that it can be hard to > estimate), email notification when it's done, adding more "workers", > would be nice. In any case, the message that version is ready to start > serving upon upload is misleading. version might be capable of serving > http requests, but it all indexes inindex.yaml aren't built you > should get a warning at least > > On a separate note, vacuum_indexes more often than not, hangs. Well, > maybe it isn't hung, but it appears so, because output just says > Fetchingindexdefinitions diff, and stale indexes still show in the > console. > > On May 1, 2:02 am, "Jason (Google)" <[email protected]> wrote: > > > Hi Alex. We definitely need to (and will) document this better, butindex > > build time is not directly proportional to the number of entities in the > > datastore but to the number of other applications who arebuildingindexes > > at the same time. Sinceindexbuildingis managed by a fixed number of > > "workers," your application's indexes will take longer to build if there are > > a higher number of applicationsbuildingindexes. It appears that this > > particular issue affected a number other developers earlier in the week. > > We'll take a closer look at this problem and how it can be better mitigated > > going forward, but it should be fairly uncommon for the most part. > > > - Jason > > > On Mon, Apr 27, 2009 at 11:30 PM, Alex Popescu < > > > [email protected]> wrote: > > > > Is there any status update on this issue? I have noticed other posts > > > on the list speaking about the same problem. > > > > ./alex > > > > On Apr 27, 2:59 pm, Alex Popescu <[email protected]> > > > wrote: > > > > Hi, > > > > > I have defined a newindexfor an entity based on a datetime and 1char > > > > string property. Currently there are only 58 such entities in the > > > > datastore and after 1h15min it is still not ready. I do not see any > > > > reasons whybuildingtheindexfor such a small amount of entities > > > > would take such a long time, except a problem with the backend. > > > > > The application id: dailycloud. > > > > > ./alex --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
