Does this means that If I migrate my app use the High Replication
Datastore, the issue with the DatastoreTimeoutException will go away?
If the DatastoreTimeoutException is related due to a M/S issue at the
moment, then yes.
Cheers,
Jose
--
You received this message because you are
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
