My suggestion in this case is pretty simple: test, test and test. If you
setup 2 nodes, for example on Amazon EC2 (low cost, on demand), one filled.
One not started. You start the other one. Wait for it to have replicated.
Shut down the old one. Verify everything is there and working.
Another tip: backup everything on the old node and store it somewhere safe.
Just my 2 cents.
Disclaimer: The information contained in this message and attachments is
intended solely for the attention and use of the named addressee and may be
confidential. If you are not the intended recipient, you are reminded that
the information remains the property of the sender. You must not use,
disclose, distribute, copy, print or rely on this e-mail. If you have
received this message in error, please contact the sender immediately and
irrevocably delete this message and any copies.
2012/9/19 Eugene Strokin firstname.lastname@example.org
I need to move my ES cluster to different DC with zero down time.
My Idea was just to add a node on the other DC and when all data is
replicated to there, shut down the original node, and use the new one. I
assume that it will become a master once the original master will go down.
Reading other's experience, I'm getting mixed fillings about all this.
As of now, I'm trying to compile my todo list, one item will be to add a
file to /etc/sysctl.d/ that contained net.ipv4.tcp_keepalive_time = 1800
to keep ES from beaching yellow.
Does anybody has such experience? And could some one point to some
possible problems/solutions related to the subject?
Thanks in advance,