Hi lein, When there is a collision on a write to the datastore, the transaction is retried automatically. This is part of the reason why collisions can be so expensive and should be avoided :-) Several of the videos on App Engine from Google I/O contain some advice and best practices for datastore operations: http://sites.google.com/site/io/
Happy coding, Jeff On Aug 29, 2:59 pm, Iein <[EMAIL PROTECTED]> wrote: > Hi folks... > > I'm working on a high transaction volume application and we've been > doing some load testing. We're encountering the following warning > messages on a number of high contention entities that we're updating > inside transactions: > > Transaction collision for entity group with key > datastore_types.Key.from_path(xx) > > I'm wondering how to precisely interpret this specific message, i.e. > did the original transaction fail and then attempt retry? > On certain requests the message is logged multiple times. Any > information would be appreciated. > > Thanks. > > PS - the key path from the warning message was purposely omitted --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
