[google-appengine] Re: Massive HR Datastore failing. Transaction committed but old data coming back on read.

2012-03-26 Thread jon
We've just received user reports and we haven't had a chance to investigate fully but I think we're experiencing an identical issue. Our users report that their recorded actions in the past 1-2 hours aren't always visible when the data is read from the datastore. Ray is the problem caused by get_

[google-appengine] Re: Massive HR Datastore failing. Transaction committed but old data coming back on read.

2012-03-26 Thread jon
Yep I've confirmed that we are suffering an identical problem. I've opened a production issue here: http://code.google.com/p/googleappengine/issues/detail?id=7219 I wouldn't mind you starring the issue too, Ray. On Mar 27, 2:59 pm, jon wrote: > We've just received user reports and we haven't ha

[google-appengine] Re: Massive HR Datastore failing. Transaction committed but old data coming back on read.

2012-03-26 Thread Ray
I am not sure if it is the identical issue, but HR datastore is definitely having big problem for me. My main concern is data is committed within transaction but after a few hours, old data would be retrieved even with get_by_id. (Not because of cached in memcache/client/etc). No user is repo