I'll raise the issue with some other members of the team, but it seems like this is working as expected. A memcache namespace is nothing more than a prefix applied to a memcache key. There's no true partitioning mechanism within memcache. grabTail simply returns the item that would be expired by the LRU mechanism if memcache needed more space. There isn't a different "queue" per namespace, only a "queue" for global expirations.
On Mon, Feb 1, 2010 at 4:29 AM, phraktle <[email protected]> wrote: > Hi, > > On production, grabTail returns objects from other namespaces. This is > a significant problem that > makes grabTail (thus queue-like usage) unusable. > > I filed this as a bug, with a very simple example here: > http://code.google.com/p/googleappengine/issues/detail?id=2706 > > Can you please look into this? I don't even see a workaround that I > can implement in the meantime... > > Thanks, > Viktor > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine-java%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- Ikai Lan Developer Programs Engineer, Google App Engine http://googleappengine.blogspot.com | http://twitter.com/app_engine -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
