We did this as well, pretty much the same as Wido.
We had a fiber connection with good latency between the locations.
We installed a virtual monitor in the destination datacenter to always
keep quorum then we
simply moved one node at a time after setting noout.
When we took a node up on the destination we had a small moving of data
then the cluster
was back to healthy again.
We had a higher apply and commit latency until we all the nodes was on
the destination
side but we never noticed any performance issues that caused issues for us.
Best regards
On 1/28/20 1:30 PM, Wido den Hollander wrote:
On 1/28/20 11:19 AM, Marc Roos wrote:
Say one is forced to move a production cluster (4 nodes) to a different
datacenter. What options do I have, other than just turning it off at
the old location and on on the new location?
Maybe buying some extra nodes, and move one node at a time?
I did this ones. This cluster was running IPv6-only (still is) and thus
I had the flexibility of new IPs.
First I temporarily moved the MONs from hardware to Virtual. MONMAP went
from 3 to 5 MONs.
Then I moved the MONs one by one to the new DC and then removed the 2
additional VMs.
Then I set the 'noout' flag and moved the OSD nodes one by one. These
datacenters were located very close thus each node could be moved within
20 minutes.
Wait for recovery to finish and then move the next node.
Keep in mind that there is/might be additional latency between the two
datacenters.
Wido
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
