"As the documentations says, to avoid this you would need to implement idempotent transactions, but its better to attack the underlying problem (Datastoretimeout exception). Because your app is on M/S, this could explain why you are getting this exception in a low rate. You can mitigate this by migrating your application to High Replication datastore."
Does this means that If I migrate my app use the High Replication Datastore, the issue with the DatastoreTimeoutException will go away? In fact I'm considering such migration, because my app is fully rewritten to use twig-persist instead of JDO (a new version of the application) and I have to migrate 90% of the existing data to a new GAE app (due m-s -> HRD migration restriction I have to create another app). I also have to consider some consistency issues that are described in http://code.google.com/appengine/docs/java/datastore/hr/overview.html. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/CLFW3DcEnWwJ. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
