Actually I think it's because one group of systems is 32 bit and the others are 64 bit, so hash() returns a larger integer.
On 4/27/07, Kevin Lewandowski <[EMAIL PROTECTED]> wrote:
I've found the problem. The Python client uses the "hash" function to determine the server for lookup and storage. My existing servers were running Python 2.3.5 but my new ones run Python 2.3.4. And it looks like those versions return a different hash value for the same key. bad. Thanks all for your suggestions. On 4/27/07, Dustin Sallings <[EMAIL PROTECTED]> wrote: > > > > On Apr 27, 2007, at 11:13 , Kevin Lewandowski wrote: > > > I've been successfully running memcached across 4 nodes for several > > years with no problems. I just recently added more nodes and now I > > noticed memcached is storing the same key on more than one node. > > > > > Has this happened to anyone before? I'm really not sure what could be > > causing this. I'm using the python client via apache. > > The memcacheds aren't aware of each other. They operate as independent > storage nodes. > > What's likely happened is that you have different configs on one of your > clients, or you're seeing older data (i.e. values stored before the new > nodes were added). > > -- > Dustin Sallings > >
