On Fri, May 24, 2013 at 9:01 AM, Hiller, Dean <dean.hil...@nrel.gov> wrote: > I seem to remember problems with ghost nodes, etc. and I seem to remember if > you are replacing a node and you don’t use the same ip, this can cause > issues. Is this correct?
If you don't use replace_token, this won't work at all. You'll get "attempt to bootstrap node into range of live node" type error, because the old ip will still own the token. If you do use replace_token, there have been historical cases where you get (non-service-impacting) ghost node state. > We would like the new node to keep the same token, and the same host name but > are wondering if we can change the ip since we are bringing the new node up > in a new rac that has a 10Gb switch. replace_token is your friend. note however that replace_token is effectively a bootstrap, so you will end up with duplicate/extra data. :) =Rob
