Indexes in Error State

2 views
Skip to first unread message

Ishmael

unread,
Jul 1, 2009, 1:35:34 PM7/1/09
to Google App Engine
Dear Google?:

I have two indexes in an Error state. I've removed them from
index.yaml and deployed. Then ran vacuum_indexes which said it was
"Deleting selected index definitions" after I entered "y" to both.

However, they are still in the Error state and I was wondering if
there is anything else I need to do?

Do I just keep waiting? It's been awhile. :)

Ishmael

unread,
Jul 1, 2009, 1:38:01 PM7/1/09
to Google App Engine

Forgot to include my App ID: dd-pdigm and the Indexes are for
"PlaceHoodIndex" and "PlaceTagIndex" entities.

Ishmael

unread,
Jul 2, 2009, 8:02:40 AM7/2/09
to Google App Engine
It's been more than 24 hours now and my Indexes are both still in the
Error State!

I've been using App Engine for nearly a year now and every time I post
to this group I NEVER get a response. Our application is in a
production state and I realize this product is in Beta, but WHY CAN'T
I DELETE MY INDEXES?

I've found countless posts on here where someone asked this question
and a Google Employee replied saying they had done something on the
backend so the indexes could be vacuumed. I've tried all of the
methods I've found - THIS IS NOT A CASE OF SOMEONE WHO JUST
IMMEDIATELY POSTS TO THE GROUP WITHOUT SEARCHING AND TRYING TO FIX IT
THEMSELVES.

Will someone please do whatever needs to be done to my two Indexes:

App ID: dd-pdigm
Indexes: PlaceHoodIndex, PlaceTagIndex

This app is tied to a Google Apps domain, and we are an authorized
Google Apps Reseller.

PLEASE HELP!

Wooi Koay

unread,
Jul 2, 2009, 9:51:47 AM7/2/09
to Google App Engine
What I did, as a temporary work around until the index problem is
fixed, was to modify my query slightly to require a new index.

Jeff S (Google)

unread,
Jul 2, 2009, 7:26:07 PM7/2/09
to Google App Engine
Hi Ishmael,

It appears that the two indices that you mentioned were removed and
have been recreated successfully. I'm sorry I didn't get to this
sooner.

Cheers,

Jeff
Reply all
Reply to author
Forward
0 new messages