Hi Pierre-Yves, Thanks for your comments. I'm aware of what causes contention errors, and how to resolve them. However, I'm just surprised that moving from the DB (*not* NDB) library to the Cloud NDB library suddenly causes contention errors. (and it's significant; e.g. a model that never used to have problems with 20 shards now still has problems with 60 shards).
I am also aware about the caching behavior. I have not configured any cache. However, since I'm coming from DB (which isn't cached at all either), and since this is about problems with writing (which would write through the cache anyway AFAIK), I don't see how cache changes can cause this. Unfortunately, since I'm not coming from NDB, I can't say whether it's the move from DB->NDB or NDB->Cloud NDB that causes this. I did the entire jump in one time. Could you explain why you bring up 'Firebase in Datastore mode'? Am I suddenly using a different architecture by switching to a different library to access the same data? thanks, Remko -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/43384eba-3191-4d87-9be6-a86223a30c88%40googlegroups.com.
