Nick, et. al., This raises a couple questions:
> - Q: Why am I seeing > 0.1% rate of datastore operations time out and > is anything being done to reduce this? A: A certain level of datastore > timeouts is expected (generally between 0.1% and 0.2% of all datastore > operations) but, we are actively working on ways to improve datastore > reliability. If you are seeing a much higher rate, be sure to inspect > your data model for write contention which often manifests as > datastore timeouts. [9:02-9:07] 1) Is the exponential-increase backoff decorator that was posted here a good approach to deal with datastore timeouts that are *not* caused by write contention? (I think I'm seeing that same 1 per 1000 failure rate, in cases where contention is simply impossible.) 2) If not, how would you recommend dealing with this? 3) If so, why isn't this built-in to the datastore API? Handling totally random, not-our-fault exceptions seems like a really strange thing to make us do in user-space. -Joshua --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
