Memcache for our app is back now. According to the log, memcache write operations started throwing com.google.appengine.api.memcache.MemcacheServiceException at 17:49 (Melbourne time) and stopped at 18:56. In other words memcache was unavailable for over 1 hour.
We use memcache heavily, so our site would've been down for that long if we hadn't stepped in to turn off all uses of memcache. Question for Google: is there an affinity between an app and it's memcache service provider? How can memcache consistently error out for the same application for that long? On Oct 25, 6:29 pm, jon <[email protected]> wrote: > Hi, > > Writing to memcache is down for one of our apps, other apps are OK. > > The error message says: > java.lang.RuntimeException: > com.google.appengine.api.memcache.MemcacheServiceException: Memcache > put: Set failed to set 20 keys > > The affected app id: thecrowdvoice > > Could someone from Google urgently take a look please? > > Thanks in advance, > Jon -- 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.
