The more kinds that are included in a single backup job, the more likely
you are likely to encounter transaction contention when the job is starting.
There are improvements to the reduce the contention that are coming in the
next App Engine release and further improvements thereafter are planned.
To avoid this problem for now, you can split the kinds you want to backup
in a few separate backup operations.
On Thu, Aug 8, 2013 at 1:47 AM, Aswath Satrasala wrote:
> Hello,
>
> Datastore backup to Google Cloud storage.
>
> In the Data store Admin console, in the 'Completed Operations' section,
> following error is shown for the backup
>
> TransactionFailedError: The transaction could not be committed. Please try
> again.
>
> I retried the backup again, and I got the same message.
>
> Issue is also raised as a production issue :
> https://code.google.com/p/googleappengine/issues/detail?id=9809
>
> -Aswath
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine.
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.
