The way we've handled this kind of thing is to wrap the client code to do double writes; when a new cache is warmed up sufficiently the old boxes can be taken down with clients updated to only "get" from the new hosts and stop sending the old ones any further "set" commands.
<br><br><div><span class="gmail_quote">On 4/11/07, <b class="gmail_sendername"><a href="mailto:rkmr.em@gmail.com">rkmr.em@gmail.com</a></b> <<a href="mailto:rkmr.em@gmail.com">rkmr.em@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
i get it .. it is jus that memcache is so awesome.. and it doest feel all that good losing the cache.. when there is a 90+% hit rate!! </blockquote></div><br>