Building Indexes and 500 Server Error
Joel
Anything I can do?
I have a Kind with about 30 entities in it (I think my terminology is
correct).
The kind has has 7 fixed properties and is an Expando.
I manually updated my index.yaml with 100 different indexes for this
kind.
Not very complex indexes:
- kind: Case
properties:
- name: appname
- name: casebase
- name: f99
The upload of the index.yaml got a server error.
Looking at my indexes through my AppEngine console I see that 87 of
them made it.
If I simplify my index.yaml and remove those 87 that made it and try
again I get:
Uploading index definitions.
Error 500: --- begin server output ---
Server Error (500)
A server error has occured.
--- end server output ---
Furthermore, my indexes are still building.
1) The 'A server error has occured' output is frustrating - there
isn't anything informative about it. Is it my fault? Is it
Google's? How can it be fixed?
2) Waiting for indexes to build is really annoying. It'd be nice to
know that progress is being made: Where am I in the queue? Is there a
problem with my indexes?
If there's something I can do I'd love to do it.
If there's something Google can tell me I'd love that too :-)
(What I'm afraid of is that I'm going to end up in a stuck state,
unable to add or change anymore indexes, much less run my app.)
Joel
Joel
http://code.google.com/p/googleappengine/issues/detail?id=287&q=index&colspec=ID%20Type%20Status%20Priority%20Stars%20Owner%20Summary
(so that's where the over quota note on my dashboard is coming from)
That seems to be saying you can't have more than 100 indexes.
This seems to go against the concepts in the google IO talk about
under the covers of the datastore... that one shouldn't worry about
optimizing indexes and worry more about using the datastore.
(My indexes are still building... I'd sure love to cancel them, delete
them, and
put a subset in of what I want!)
On Jun 27, 6:33 pm, Joel <joel.riede...@gmail.com> wrote:
> More fun withindexes.
>
> I have a Kind with about 30 entities in it (I think my terminology is
> correct).
> The kind has has 7 fixed properties and is an Expando.
> I manually updated my index.yaml with100differentindexesfor this
> kind.
> Not very complexindexes:
>
> - kind: Case
> properties:
> - name: appname
> - name: casebase
> - name: f99
>
> The upload of the index.yaml got a server error.
>
> If I simplify my index.yaml and remove those 87 that made it and try
> again I get:
> Uploading index definitions.
> Error 500: --- begin server output ---
>
> Server Error (500)
> A server error has occured.
> --- end server output ---
>
> 1) The 'A server error has occured' output is frustrating - there
> isn't anything informative about it. Is it my fault? Is it
> Google's? How can it be fixed?
> problem with myindexes?
>
> If there's something I can do I'd love to do it.
> If there's something Google can tell me I'd love that too :-)
>
> (What I'm afraid of is that I'm going to end up in a stuck state,
>
> Joel
Edward A Robinson
get the error when I try to upload my full app, any help Marizia?
On Tue, Sep 16, 2008 at 10:52 AM, Joel Riedesel <joel.r...@gmail.com> wrote:
> Try clearing your application
> (make an empty directory with only an empty app.yaml (except for your
> project name stuff) in it and do an update with that)
>
> Then vacuum the indexes
>
> Then try again with the real application.
>
> Still have problems post a note on the list and hopefully Marizia (sp?)
> will get someone to look at your app.
>
> Joel
>
> earobinson wrote:
>> Anyone know how to blow all of your index definitions. away and start
>> over I cant seem to get rid of the
>>
>> Uploading index definitions.
>> Error 500
>>
>> error.
>>
>> On Jun 27, 10:35 pm, Joel <joel.riede...@gmail.com> wrote:
>>> I just found issue 287http://code.google.com/p/googleappengine/issues/detail?id=287&q=index...
>>> (so that's where the over quota note on my dashboard is coming from)
>>>
>>> That seems to be saying you can't have more than 100 indexes.
>>>
>>> This seems to go against the concepts in the google IO talk about
>>> under the covers of the datastore... that one shouldn't worry about
>>> optimizing indexes and worry more about using the datastore.
>>>
>>> (My indexes are still building... I'd sure love to cancel them, delete
>>> them, and
>>> put a subset in of what I want!)
>>>
>>> On Jun 27, 6:33 pm, Joel <joel.riede...@gmail.com> wrote:
>>>
>>>> More fun withindexes.
>>>> Anything I can do?
>>>> I have a Kind with about 30 entities in it (I think my terminology is
>>>> correct).
>>>> The kind has has 7 fixed properties and is an Expando.
>>>> I manually updated myindex.yaml with100differentindexesfor this
>>>> kind.
>>>> Not very complexindexes:
>>>> - kind: Case
>>>> properties:
>>>> - name: appname
>>>> - name: casebase
>>>> - name: f99
>>>> The upload of theindex.yaml got a servererror.
>>>> Looking at myindexesthrough my AppEngine console I see that 87 of
>>>> them made it.
>>>> If I simplify myindex.yaml and remove those 87 that made it and try
>>>> again I get:
>>>> Uploadingindexdefinitions.
>>>> Error500: --- begin server output ---
>>>> ServerError(500)
>>>> A servererrorhas occured.
>>>> --- end server output ---
>>>> Furthermore, myindexesare still building.
>>>> 1) The 'A servererrorhas occured' output is frustrating - there
>>>> isn't anything informative about it. Is it my fault? Is it
>>>> Google's? How can it be fixed?
>>>> 2) Waiting forindexesto build is really annoying. It'd be nice to
>>>> know that progress is being made: Where am I in the queue? Is there a
>>>> problem with myindexes?
>>>> If there's something I can do I'd love to do it.
>>>> If there's something Google can tell me I'd love that too :-)
>>>> (What I'm afraid of is that I'm going to end up in a stuck state,
>>>> unable to add or change anymoreindexes, much less run my app.)
>>>> Joel
>>
>
--
Edward A Robinson -- www.earobinson.org