Thanks for sharing retrying, indeed it's pretty interesting My situation is pretty unique, that's why there are usually 3 consecutive requests in the worst case and at most 5-6, that's why an architecture change is an overkill
I had a lot of experience with both push queue and pull queue based solutions in the past, and I can safely say that, "better let them content" In my opinion, both pull queues and push queues are extremely unreliable, so on this project, I made it so that the occasional contention is safe to occur However, I hoped with retries=6 the transactions would untangle them on their own, but they don't -- 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 https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/64683751-e390-4f16-ad0c-ec4a94246256%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
