Is there any possibility your datastore calls are hitting the 30s timeout? There's no transactional link between datastore and memcache, and Objectify writes to memcache only after a successful datastore write. If you hit the 30s timeout while blocked in a write (which actually succeeds), you can get the cache out of sync.
Jeff On Fri, Feb 25, 2011 at 9:05 AM, David <[email protected]> wrote: > Ever since the last update I've been having issues with my app > returning stale data. I thought it was a bug in the client that was > reading the data, but as it turns out I tracked it down to the > memcache entity being out of sync from the datastore entity where the > memcache information is older than what is in the datastore. I'm > using Objectify as my interface in java which is very simple. It just > writes to memcache when it writes to the datastore. It's been working > fine for the past 6 months my app has been around. It could also be > because the past couple of months I've been experiencing problematic > latency errors in the datastore, but it still seems awfully > coincidental that there was a change to the memcache api related to > not persisting information if it has changed. > > Has anyone else noticed similar behavior? > > Thanks, > David > word-play.appspot.com > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > 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. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. 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.
