Hi, My indexes (2 of 2) are unfortunately stuck on "Building" even though I have little data and have tried a few update and vacuum index commands. Could someone from the AppEngine team take a look and reset my indexes to "Error" ?
Thanks heaps. On 10 Tháng Tám, 22:04, "Nick Johnson (Google)" <nick.john...@google.com> wrote: > Hi Bryan, > > I've reset your indexes again. > > We are working on improving theindexbuilding system to the point > where this will no longer be an issue. > > -Nick Johnson > > > > > > On Mon, Aug 10, 2009 at 3:29 PM, Bryan Pendleton<bpendle...@gmail.com> wrote: > > It was cleared, but now I seem to have re-introduced the problem as a result > > of a poor re-shuffle of myindex.yaml file. > > Is there a reason that either: > > 1) More reporting than "Error" is not provided? > > 2) Users can't be offered a self-help un-stick, perhaps limited to trying > > 1x/hour or something? Or am I doing something so wrong that it should never > > happen and, thus, stick the indexes? > > -- > > Bryan A. P. Pendleton > > > On Mon, Aug 10, 2009 at 9:27 AM, Nick Johnson (Google) > > <nick.john...@google.com> wrote: > > >> Hi Bryan, > > >> Please try vacuuming and rebuilding your indexes now. > > >> -Nick Johnson > > >> On Sat, Aug 8, 2009 at 6:29 PM, Bryan Pendleton<bpendle...@gmail.com> > >> wrote: > >> > My indexes are stuck, on application "aquarium-bp". Oneindexis in > >> > error, > >> > the rest are "building". When I attempt to vacuum with a > >> > no-indexes-defined > >> >index.yaml file, I'm offered the opportunity to delete each, in turn. > >> > If I only choose "yes" for the Errorindex, I get the "Deleting selected > >> >indexdefinitions.", but theindexnever disappears (and remains > >> > "Error"). > >> > If I say "yes" to delete any other indexes, I'm given the somewhat more > >> > confusing "2009-08-08 13:20:20,689 WARNING appcfg.py:704 Anindexwas > >> > not > >> > deleted. Most likely this is because it no longer exists." message, and > >> > still nothing changes. > >> > I have a fairly small amount of data in my Datastore, but this broken > >> > application state is making it impossible for me to continue > >> > development/deployment of my app, which is now (further) behind > >> > schedule. > >> > Could someone from the AppEngine team take a look and maybe knock my > >> > indexes > >> > loose? > >> > -- > >> > Bryan A. P. Pendleton > >> > Graduate Student, Carnegie Mellon Human Computer Interaction Institute > >> > Ph: (877) geek-1-bp > > >> > On Thu, Jun 4, 2009 at 1:40 PM, Nick Johnson (Google) > >> > <nick.john...@google.com> wrote: > > >> >> Hi, > > >> >> I've reset your indexes to 'error' state. You can now vacuum and > >> >> recreate > >> >> them if you wish. > > >> >> -Nick Johnson > > >> >> On Wed, Jun 3, 2009 at 10:07 PM, mmiy...@gmail.com <mmiy...@gmail.com> > >> >> wrote: > > >> >>> Hi, > >> >>> I've got a problem while building a newindexfor my applicaiton. > >> >>>index.yaml is correctly uploaded but its status is stacked in > >> >>> "Building" for a week. Something must be wrong. > >> >>> I've tried vaccuming theindexby appcfg.py but failed... I need some > >> >>> help. My application ID is "codepasture-rest". > >> >>> Thanks. > > >> -- > >> Nick Johnson, Developer Programs Engineer, App Engine > > -- > Nick Johnson, Developer Programs Engineer, App Engine --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
