On Wed, 29 Jul 2009, blazah wrote:
Hi,
What do folks do with the objects stored in memcached when a new
version of the software is deployed? There is the potential that the
data could be stale depending on the code changes so do people
typically just flush the cache?
Generally you know
Hey,
You might want to consider using 'add' with a zero byte value (or just a
single byte value, whatever). Then every time you just run the single add
command. If it fails you're fetching too fast. If it works then the key
didn't exist already.
There're a bunch of ways of doing more proper
I wouldn't recommend anyone use the ALLOW_SLABS_REASSIGN code as it is -
it is unproven and we probably should have removed it a long time ago.
It'll come back as a proper implementation soon enough.
-Dormando
On Tue, 28 Jul 2009, Mike Lambert wrote:
Werner you never mentioned which version
Yo,
Updates to the issue tracker should now all hit the mailing list. The
traffic over there is relatively low, but only a small handful of us
actively check it - I'd prefer all information go to the same place. A few
threads which should have been mailing list discussions have instead been
held
Hey,
I read the whole thread and thought about it for a bit... I'm not sure we
should do this. Especially not as an explicit solution to a security
problem with a shared hosting cluster. We can roadmap out a method of
multitenancy (dustin's apparently done proof of concept before, and I can
dormando wrote:
Yo,
Updates to the issue tracker should now all hit the mailing list. The
traffic over there is relatively low, but only a small handful of us
actively check it - I'd prefer all information go to the same place.
I think this is a good change...
A few
threads which should
Awesome! I think this is a handy change to get potential bugs
identified and fixed as soon as possible.
On Aug 3, 2009, at 5:50 PM, dormando dorma...@rydia.net wrote:
Yo,
Updates to the issue tracker should now all hit the mailing list. The
traffic over there is relatively low, but only
Yeah, I'm inclined to agree with you... Disabling flush seems like a bit of
a red herring. Sure, it prevents one very particular case, but at best it
provides a false sense of safety.
If we were going to do anything like this, perhaps we could consider doing
something like how Tokyo
I'm not seeing many examples on the web using memcache and python. Can
someone show me a quick sample of how to set up, add and retrieve data
from memcache?
thanks,
JJ
There is an easy to use pure python module called python-memcached available
at tummy.com:
http://www.tummy.com/Community/software/python-memcached/
You can install it by doing:
easy_install python-memcached
If you look at the memcache.py script, you'll see a usage example in the
tests towards
No, it isn't, check out this to read more:
http://code.google.com/p/memcached/wiki/FAQ#Can_I_iterate_the_items_of_the_memcached_server?
2009/8/3 Jeremiah Jester jeremiahjes...@gmail.com:
Thanks.
Also, another question...
Is there a way in php to retrieve a list of all set keys and data for
The memcached FAQ links to this document describing the binary protocol:
http://code.google.com/p/memcached/wiki/MemcacheBinaryProtocol
Unfortunately, this document is out of date compared to the
protocol-binary.xml that ships with 1.4.0. For example, it is missing
various opcodes like
On Aug 3, 7:37 pm, Mat Hostetter mjhostet...@gmail.com wrote:
The memcached FAQ links to this document describing the binary protocol:
http://code.google.com/p/memcached/wiki/MemcacheBinaryProtocol
Unfortunately, this document is out of date compared to the
protocol-binary.xml that
Status: Accepted
Owner: dsallings
Labels: Type-Defect Priority-Medium
New issue 70 by dsallings: Incorrect data type when referencing the data
size of an item.
http://code.google.com/p/memcached/issues/detail?id=70
The item struct records the number of bytes as an int. This should be
Updates:
Status: New
Comment #1 on issue 68 by dsallings: incr/decr resize corruption
http://code.google.com/p/memcached/issues/detail?id=68
I'm marking this as new as opposed to accepted since accepted implies
that the
problem has been reproduced. Here I'm just recording something
15 matches
Mail list logo
