On Apr 16, 12:08 pm, ryan <ryanb+appeng...@google.com> wrote:
> the discussion here is pretty on target. thanks, all!
>
> beyond the points already raised, i'd guess this is caused either by
> writes (puts or deletes) that returned errors, and therefore didn't
> update all indices, or an index consistency bug that we're currently
> working on:
>
> http://code.google.com/p/googleappengine/issues/detail?id=901
>
> in both cases, a successful put() on the entity in question will fix
> the problem. we're still working on issue 901, and we definitely
> expect to have that resolved soon. as for put() and delete() calls
> that return errors (like timeouts), we're always working to reduce
> those, but they'll unfortunately always be possible, so you'll want to
> plan for that.
What is the recommended way to deal with such an error? I'd be okay
with the put failing entirely, or eventually updating the indexes
automatically once the situation resolves, but partially updating
indexes sounds like it can only lead to trouble - particularly if the
error condition preventing the put from completing continues for an
extended period of time (how long do tablet servers take to be
replaced if one fails?)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
