Article ID: 118236, created on Oct 28, 2013, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo

Answer

Changing the IP address that MDS server is bound to is possible, starting from PCS 6 update 4. This is possible with pstorage -c <clustername> configure-mds utility. For more information check man pstorage-configure-mds.

Here's an example, showing how to change the network of the cluster.

Let us suppose you have a cluster "mycluster", consisting of three hosts with metadata servers:

host1 with MDS#1, 10.10.10.1:2510
host2 with MDS#2, 10.10.10.2:2510
host3 with MDS#3, 10.10.10.3:2510

And you want to move the metadata servers to a new network 10.10.20.0/24.

To do this, execute the following commands on each host (it is highly recommended to back up all MDS repositories before doing this):

#1 [root@host1] service pstorage-mdsd stop
#2 [root@host1] pstorage -c mycluster configure-mds -r /mnt/storage/mds -N -n 1@10.10.20.1:2510 -n 2@10.10.20.2:2510 -n 3@10.10.20.3:2510
#3 [root@host1] service pstorage-mdsd start

#4 [root@host2] service pstorage-mdsd stop
#5 [root@host2] pstorage -c mycluster configure-mds -r /mnt/storage/mds -N -n 1@10.10.20.1:2510 -n 2@10.10.20.2:2510 -n 3@10.10.20.3:2510
#6 [root@host2] service pstorage-mdsd start

#7 [root@host3] service pstorage-mdsd stop
#8 [root@host3] pstorage -c mycluster configure-mds -r /mnt/storage/mds -N -n 1@10.10.20.1:2510 -n 2@10.10.20.2:2510 -n 3@10.10.20.3:2510
#9 [root@host3] service pstorage-mdsd start

Note: The cluster will be unavailable while commands #4 to #6 are executed! Afterwards, make sure you reconfigure discovery parameters (also described in man pstorage-discovery).

Additional information

Prior to PCS 6 update 4, the only solution is to do the following:

  1. Remove the IP address from eth0

  2. Assign the same IP address on the eth1 network interface

  3. Restart the mds service by using the following command:

    /etc/init.d/pstorage-mdsd
    

Search Words

pstorage

Change PCS Chunk MD and Client IP

configure-mds

mds

storage ip

ip address

chunk

change

network

2897d76d56d2010f4e3a28f864d69223 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF