Re: replacing/migrating memcache servers

Coolio.. that was helpful.. thanks! On Tue, Jun 28, 2016 at 12:20 AM, dormando wrote: > +1. > > On Mon, 27 Jun 2016, 'Jay Grizzard' via memcached wrote: > > > This is really heavily dependent on the exact hashing algorithm your > library. Some are (relatively) good about

Re: replacing/migrating memcache servers

+1. On Mon, 27 Jun 2016, 'Jay Grizzard' via memcached wrote: > This is really heavily dependent on the exact hashing algorithm your library. > Some are (relatively) good about losing a server, others are complete trash > about it. I don’t > know what the perl lib does off the top of my head. >

Re: replacing/migrating memcache servers

This is really heavily dependent on the exact hashing algorithm your library. Some are (relatively) good about losing a server, others are complete trash about it. I don’t know what the perl lib does off the top of my head. I’m assuming new-memcache01 is the mcrouter box? If so, you might

Re: replacing/migrating memcache servers

On Mon, 27 Jun 2016, Geoff Galitz wrote: > Hi... > We're working on a project to migrate from one set of memcache servers to > newer largers ones which are behind a mcrouter. > > One option on the table is to take the current memcache_servers array in our > perl app and replace a single