Deleting index stuck

[Nick Winter]

Our app (skrit) was missing an index, so we tried to add it, but it
showed up as "Error". Then we tried to vacuum it in order to add it
again, but it's just been stuck on "Deleting" for two days. Repeated
vacuuming says that it couldn't delete it because it probably doesn't
exist.

We tried working around it by creating a similar index, but we really
do need that specific one. After looking around, it seems people have
solved stuck index problems either by uploading an empty app and then
reuploading the entire project and data, switching to a new app space,
or by asking someone from Google to take a look. We don't have many
users yet, but we do have a lot of data that would hurt to reupload,
so I was wondering if someone might help us out?

[Marzia Niccolai]

Hi Nick,
 Our engineering team is looking in to it, when I have more information I can follow up with you directly.

Thanks,
Marzia

[Nick Winter]

Thanks, Marzia!

[AK]

Hey Marzia,

I am having the exact same issue as Nick. I tried vacuuming the index
to delete but its been stuck on 'deleting'. My appname is
'supercharmedpilot'. Looking forward to your update.

Thanks in advance !


Cheers,

Avlok

On Sep 9, 1:40 pm, "Marzia Niccolai" <ma...@google.com> wrote:
> Hi Nick,
>  Our engineering team is looking in to it, when I have more information I
> can follow up with you directly.
>
> Thanks,
> Marzia
>

[tigrillo]

Hello, I share the trouble (can not delete an index with "building"
status nor update_indexes), notify me also, Thanks

[Martynas Brijunas]

Hi, same here, the index is stuck on "Deleting", the app name is
"gentlecolours". Thanks!

[Marzia Niccolai]

Hi,

Your indexes are now in the 'Error' state, and you should be able to vacuum and re-upload the indexes.

-Marzia

[Josh]

Marzia,

I'm having problems with a lot of stuck indexes that won't delete as
well, and uploading gives me "building a composite index failed:
ApplicationError 3"

Would you be able to help me out please? My app ID is lplanet.

Thanks,

Josh

On Sep 25, 1:53 am, "Marzia Niccolai" <ma...@google.com> wrote:
> Hi,
>
> Your indexes are now in the 'Error' state, and you should be able to vacuum
> and re-upload the indexes.
>
> -Marzia
>

[Derrick]

I am having the same issue. My application is "vhac".

Thanks.

[Marzia Niccolai]

Hi Derrick,

This index has deleted.  Sometimes it can take a few hours to upload/delete index definitions.

-Marzia

[Rajkumar Radhakrishnan]

Hi,

I have an app ("matrimonyplanner") which has 3 indexes stuck in "Error" state.
Tried the vacuum_indexes procedure, so as to upload them again, but it does not go into "Deleting" state and remains in "Error".

Any tips on how to proceed ?

Regards,
Rajkumar

[ryan]

have you read:

http://code.google.com/appengine/kb/general.html#error_indexes
http://code.google.com/appengine/docs/python/datastore/queriesandindexes.html#Big_Entities_and_Exploding_Indexes

[Rajkumar Radhakrishnan]

Yes, I have read them and had even tried the vacuum_indexes procedure. It did not work, as I had mentioned in my mail.

Tried it again today and they got deleted at once from my indexes.

By the way, the problem is not related to exploding indexes - there were 3 new indexes of 2 to 3 properties each, all properties were string/integer properties and the data to be indexed was less than 100. 

I just discovered that it *might* be because one of the index definition had a non-existing property name specified. I am not going to try it again with a wrong property name in the index, to confirm the reason for the "Error" :-). But, just in case any of you face a similar problem, see if this might be the reason.

Regards,

R.Rajkumar

[garyo]

I am having this problem as well.

I have vacuumed, deleting ALL indexes from index.yaml
Two indexes are stuck in an error state, and have not cleared for over
24 hours
One of the indexes has a misspelled property (__key_)
appid=gdodemo

Tag
prefix ▲ , __key_ ▲ Error
prefix ▲ , word ▲ Error

I tried a couple of more cycles, one with index.yaml empty,
and one with just the Tag entity indexes removed.

Last message was, trying to vacuum with an empty index.yaml:
Are you sure you want to delete this index? (N/y/a): a

Deleting selected index definitions.2009-06-13 13:35:47,960 WARNING
appcfg.py:670 7 indexes were not deleted. Most
likely this is because they no longer exist.

My application is currently down hard.
Without indexes, nothing will work!

On May 17, 7:43 pm, rraj <r.rajku...@gmail.com> wrote:
> Yes, I have read them and had even tried the vacuum_indexes procedure. It
> did not work, as I had mentioned in my mail.
>
> Tried it again today and they got deleted at once from my indexes.
>
> By the way, the problem is not related to exploding indexes - there were 3
> new indexes of 2 to 3 properties each, all properties were string/integer
> properties and the data to be indexed was less than 100.
>
> I just discovered that it *might* be because one of the index definition had
> a non-existing property name specified. I am not going to try it again with
> a wrong property name in the index, to confirm the reason for the "Error"
> :-). But, just in case any of you face a similar problem, see if this might
> be the reason.
>
> Regards,
> R.Rajkumar
>
> On Mon, May 18, 2009 at 2:20 AM, ryan

> <ryanb+appeng...@google.com<ryanb%2Bappeng...@google.com>

>
> > wrote:
>
> > have you read:
>
> >http://code.google.com/appengine/kb/general.html#error_indexes
>

> >http://code.google.com/appengine/docs/python/datastore/queriesandinde...

[garyo]

Well...
All indexes finally moved into an error state.
I was then able to delete them all.

Then reinstate my index.yaml.

On Jun 13, 3:48 pm, garyo <garyor...@gmail.com> wrote:
> I am having this problem as well.
>
> I have vacuumed, deleting ALL indexes fromindex.yaml
> Two indexes are stuck in an error state, and have not cleared for over
> 24 hours
> One of the indexes has a misspelled property (__key_)
> appid=gdodemo
>
> Tag
> prefix ▲ , __key_ ▲ Error
> prefix ▲ , word ▲ Error
>

> I tried a couple of more cycles, one withindex.yaml empty,

> and one with just the Tag entity indexes removed.
>
> Last message was, trying to vacuum with an emptyindex.yaml:
> Are you sure you want todeletethisindex? (N/y/a): a
>

> Deleting selectedindexdefinitions.2009-06-13 13:35:47,960 WARNING

> appcfg.py:670 7 indexes were not deleted. Most
> likely this is because they no longer exist.
>
> My application is currently down hard.
> Without indexes, nothing will work!
>
> On May 17, 7:43 pm, rraj <r.rajku...@gmail.com> wrote:
>
> > Yes, I have read them and had even tried the vacuum_indexes procedure. It
> > did not work, as I had mentioned in my mail.
>
> > Tried it again today and they got deleted at once from my indexes.
>
> > By the way, the problem is not related to exploding indexes - there were 3
> > new indexes of 2 to 3 properties each, all properties were string/integer
> > properties and the data to be indexed was less than 100.
>

> > I just discovered that it *might* be because one of theindexdefinition had

> > a non-existing property name specified. I am not going to try it again with

> > a wrong property name in theindex, to confirm the reason for the "Error"