No, you can't really lock a Memcache key. There's probably an application bug somewhere. Memcache should be strongly consistent, so any read that happens after the write should return the last written data.
I would try writing it from one instance and reading it from the same instance. Something else might be going on. Like all computer systems, there is probably *some* upper bound to Memcache's write throughput on a single value, but it should be way, way higher than 50 a second. -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Fri, Nov 4, 2011 at 5:45 PM, Andrius A <[email protected]> wrote: > What if one memcache entity is updated at the high rate (maybe 50 times > per second) could that lock it so other backends/frontends cant read it? > I am not getting any exceptions. > > > On 5 November 2011 00:40, pdknsk <[email protected]> wrote: > >> Yes, works fine here. >> >> -- >> 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. > -- 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.
