Hi Ray,

Which operation was is that timed out (get, query, put)? Also, how
consistently are you seeing these timeouts?

I generally recommend catching datastore timeouts and handling them in a way
that makes sense for your app. There are currently occasional (quite rare as
a percentage) timeouts for queries and gets, and timeouts on a put is often
an indicator of contention on that entity or entity group.

Happy coding,

Jeff

On Mon, Apr 13, 2009 at 4:11 PM, DarkCoiote <darkcoi...@gmail.com> wrote:

>
> Looks like my and others problem... posted a few days ago:
>
>
> http://groups.google.com/group/google-appengine/browse_thread/thread/83b45cb3f90a2a3f/740e922de7d0b33b?q=#740e922de7d0b33b
>
> Random datastore timeouts in totally unexpected places...
>
> On Apr 13, 2:36 pm, Ray Malone <rayish...@gmail.com> wrote:
> > I'm not sure why this occurs all of a sudden.  The same job runs in
> > 600ms.    Then once in a while this runs over 6800 MS and times out.
> > I can't have jobs just timeout for no reason.    According to my logs
> > during this time the only other request was a second prior.  This
> > occurred at 04-13 09:13AM 29.627 today and other times at random in
> > the last few days.
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to