7.2. In-Service Software Upgrade from Red Hat Gluster Storage 3.3 to Red Hat Gluster Storage 3.4
Important
Upgrade all Red Hat Gluster Storage servers before updating clients.
In-service software upgrade refers to the ability to progressively update a Red Hat Gluster Storage Server cluster with a new version of the software without taking the volumes hosted on the cluster offline. In most cases normal I/O operations on the volume continue even when the cluster is being updated.
I/O that uses CTDB may pause for the duration of an upgrade or update. This affects clients using Gluster NFS or Samba.
Note
After performing inservice upgrade of NFS-Ganesha, the new configuration file is saved as "
ganesha.conf.rpmnew" in /etc/ganesha folder. The old configuration file is not overwritten during the inservice upgrade process. However, post upgradation, you have to manually copy any new configuration changes from "ganesha.conf.rpmnew" to the existing ganesha.conf file in /etc/ganesha folder.
7.2.1. Pre-upgrade Tasks
Ensure you perform the following steps based on the set-up before proceeding with the in-service software upgrade process.
7.2.1.1. Upgrade Requirements for Red Hat Gluster Storage 3.4
The following are the upgrade requirements to upgrade to Red Hat Gluster Storage 3.4 from the preceding update:
- In-service software upgrade is supported only for nodes with replicate, distributed replicate, or erasure coded (dispersed) volumes.
- If you want to use snapshots for your existing environment, each brick must be an independent thin provisioned logical volume (LV). If you do not plan to use snapshots, thickly provisioned volumes remain supported.
- A Logical Volume that contains a brick must not be used for any other purpose.
- Only linear LVM is supported with Red Hat Gluster Storage 3.4. For more information, see https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Logical_Volume_Manager_Administration/lv_overview.html#linear_volumes
- When server-side quorum is enabled, ensure that bringing one node down does not violate server-side quorum. Add dummy peers to ensure the server-side quorum is not violated until the completion of rolling upgrade using the following command:
# gluster peer probe dummynode
Note
If you have a geo-replication session, then to add a node follow the steps mentioned in the sectionStarting Geo-replication for a New Brick or New Node in the Red Hat Gluster Storage Administration Guide.For example, when the server-side quorum percentage is set to the default value (>50%), for a plain replicate volume with two nodes and one brick on each machine, a dummy node that does not contain any bricks must be added to the trusted storage pool to provide high availability of the volume using the command mentioned above.In a three node cluster, if the server-side quorum percentage is set to 77%, bringing down one node would violate the server-side quorum. In this scenario, you have to add two dummy nodes to meet server-side quorum. - For replica 2 volumes, disable client-side quorum. This is not recommended for replica 3 volumes, as it increases the risk of split brain conditions developing.
# gluster volume reset <vol-name> cluster.quorum-type
- Stop any geo-replication sessions running between the master and slave.
# gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL stop
- Ensure that there are no pending self-heals before proceeding with in-service software upgrade using the following command:
# gluster volume heal volname info
- Ensure the Red Hat Gluster Storage server is registered to the required channels.On Red Hat Enterprise Linux 6:
rhel-x86_64-server-6 rhel-x86_64-server-6-rhs-3 rhel-x86_64-server-sfs-6
On Red Hat Enterprise Linux 7:rhel-x86_64-server-7 rhel-x86_64-server-7-rhs-3 rhel-x86_64-server-sfs-7
To subscribe to the channels, run the following command:# subscription-manager repos --enable=repo-name
7.2.1.2. Restrictions for In-Service Software Upgrade
The following lists some of the restrictions for in-service software upgrade:
- In-service upgrade for NFS-Ganesha clusters is supported only from Red Hat Gluster Storage 3.3 to Red Hat Gluster Storage 3.4. If you are upgrading from Red Hat Gluster Storage 3.1 and you use NFS-Ganesha, use the offline upgrade method instead.
- Erasure coded (dispersed) volumes can be upgraded while in-service only if the
disperse.optimistic-change-loganddisperse.eager-lockoptions are set tooff. Wait for at least two minutes after disabling these options before attempting to upgrade to ensure that these configuration changes take effect for I/O operations. - Ensure that the system workload is low before performing the in-service software upgrade, so that the self-heal process does not have to heal too many entries during the upgrade. Also, with high system workload healing is time-consuming.
- Do not perform any volume operations on the Red Hat Gluster Storage server.
- Do not change hardware configurations.
- Do not run mixed versions of Red Hat Gluster Storage for an extended period of time. For example, do not have a mixed environment of Red Hat Gluster Storage 3.3 and Red Hat Gluster Storage 3.4 for a prolonged time.
- Do not combine different upgrade methods.
- It is not recommended to use in-service software upgrade for migrating to thin provisioned volumes, but to use offline upgrade scenario instead. For more information see, Section 7.1, “Offline Upgrade to Red Hat Gluster Storage 3.4”
7.2.1.3. Configuring repo for Upgrading using ISO
To configure the repo to upgrade using ISO, execute the following steps:
Note
Upgrading Red Hat Gluster Storage using ISO can be performed only from the immediately preceding release. This means that upgrading to Red Hat Gluster Storage 3.4 using ISO can only be done from Red Hat Gluster Storage 3.3.1. For a complete list of supported Red Hat Gluster Storage releases, see Section 1.5, “Supported Versions of Red Hat Gluster Storage”.
- Mount the ISO image file under any directory using the following command:
# mount -o loop <ISO image file> <mount-point>
For example:# mount -o loop RHGS-3.4-RHEL-7-x86_64-dvd-1.iso /mnt
- Set the repo options in a file in the following location:
/etc/yum.repos.d/<file_name.repo>
- Add the following information to the repo file:
[local] name=local baseurl=file:///mnt enabled=1 gpgcheck=0
7.2.1.4. Preparing and Monitoring the Upgrade Activity
Before proceeding with the in-service software upgrade, prepare and monitor the following processes:
- Check the peer and volume status to ensure that all peers are connected and there are no active volume tasks.
# gluster peer status
# gluster volume status
- Check the rebalance status using the following command:
# gluster volume rebalance r2 status Node Rebalanced-files size scanned failures skipped status run time in secs --------- ----------- --------- -------- --------- ------ -------- -------------- 10.70.43.198 0 0Bytes 99 0 0 completed 1.00 10.70.43.148 49 196Bytes 100 0 0 completed 3.00
- If you need to upgrade an erasure coded (dispersed) volume, set the
disperse.optimistic-change-loganddisperse.eager-lockoptions tooff. Wait for at least two minutes after disabling these options before attempting to upgrade to ensure that these configuration changes take effect for I/O operations.# gluster volume set volname disperse.optimistic-change-log off # gluster volume set volname disperse.eager-lock off
- Ensure that there are no pending self-heals by using the following command:
# gluster volume heal volname info
The following example shows no pending self-heals.# gluster volume heal drvol info Gathering list of entries to be healed on volume drvol has been successful Brick 10.70.37.51:/rhs/brick1/dir1 Number of entries: 0 Brick 10.70.37.78:/rhs/brick1/dir1 Number of entries: 0 Brick 10.70.37.51:/rhs/brick2/dir2 Number of entries: 0 Brick 10.70.37.78:/rhs/brick2/dir2 Number of entries: 0
7.2.2. Service Impact of In-Service Upgrade
In-service software upgrade impacts the following services. Ensure you take the required precautionary measures.
SWIFT
ReST requests that are in transition will fail during in-service software upgrade. Hence it is recommended to stop all swift services before in-service software upgrade using the following commands:
# service openstack-swift-proxy stop # service openstack-swift-account stop # service openstack-swift-container stop # service openstack-swift-object stop
Gluster NFS
When you use Gluster NFS to mount a volume, any new or outstanding file operations on that file system will hang uninterruptedly during in-service software upgrade until the server is upgraded.
Samba / CTDB
Ongoing I/O on Samba shares will fail as the Samba shares will be temporarily unavailable during the in-service software upgrade, hence it is recommended to stop the Samba service using the following command:
# service ctdb stop ;Stopping CTDB will also stop the SMB service.
Distribute Volume
In-service software upgrade is not supported for distributed volume. If you have a distributed volume in the cluster, stop that volume for the duration of the upgrade.
# gluster volume stop <VOLNAME>
Virtual Machine Store
The virtual machine images are likely to be modified constantly. The virtual machine listed in the output of the volume heal command does not imply that the self-heal of the virtual machine is incomplete. It could mean that the modifications on the virtual machine are happening constantly.
Hence, if you are using a gluster volume for storing virtual machine images (Red Hat Enterprise Linux, Red Hat Enterprise Virtualization and Red Hat OpenStack), then it is recommended to power-off all virtual machine instances before in-service software upgrade.
Important
It is recommended to turn off all virtual machine instances to minimize the changes that occur during an In-Service Upgrade. If you choose to keep the VM instances up and running , the time taken to heal will increase and at times may cause a situation where the pending heal remains a constant number and takes a long time to close to 0.
7.2.3. In-Service Software Upgrade
If you have a CTDB environment, see Section 7.2.4.1, “In-Service Software Upgrade for a CTDB Setup”.
The following steps have to be performed on each node of the replica pair:
- Back up the following configuration directory and files in a location that is not on the operating system partition.
/var/lib/glusterd/etc/swift/etc/samba/etc/ctdb/etc/glusterfs/var/lib/samba/var/lib/ctdb/var/run/gluster/shared_storage/nfs-ganesha
If you use NFS-Ganesha, back up the following files from all nodes:/etc/ganesha/exports/export.*.conf/etc/ganesha/ganesha.conf/etc/ganesha/ganesha-ha.conf
- If the node is part of an NFS-Ganesha cluster, place the node in standby mode.
# pcs cluster standby
- Ensure that there are no pending self-heal operations.
# gluster volume heal volname info
- If this node is part of an NFS-Ganesha cluster:
- Disable the PCS cluster and verify that it has stopped.
# pcs cluster disable # pcs status
- Stop the nfs-ganesha service.
# systemctl stop nfs-ganesha
- Stop all gluster services on the node and verify that they have stopped.
# systemctl stop glusterd # pkill glusterfs # pkill glusterfsd # pgrep gluster
- Verify that your system is not using the legacy Red Hat Classic update software.
# migrate-rhs-classic-to-rhsm --status
If your system uses this legacy software, migrate to Red Hat Subscription Manager and verify that your status has changed when migration is complete.# migrate-rhs-classic-to-rhsm --rhn-to-rhsm
# migrate-rhs-classic-to-rhsm --status
- Update the server using the following command:
# yum update
- If the volumes are thick provisioned, and you plan to use snapshots, perform the following steps to migrate to thin provisioned volumes:
Note
Migrating from thick provisioned volume to thin provisioned volume during in-service software upgrade takes a significant amount of time based on the data you have in the bricks. If you do not plan to use snapshots, you can skip this step. However, if you plan to use snapshots on your existing environment, the offline method to upgrade is recommended. For more information regarding offline upgrade, see Section 7.1, “Offline Upgrade to Red Hat Gluster Storage 3.4”Contact a Red Hat Support representative before migrating from thick provisioned volumes to thin provisioned volumes using in-service software upgrade.- Unmount all the bricks associated with the volume by executing the following command:
# umount mount_point
- Remove the LVM associated with the brick by executing the following command:
# lvremove logical_volume_name
For example:# lvremove /dev/RHS_vg/brick1
- Remove the volume group by executing the following command:
# vgremove -ff volume_group_name
For example:# vgremove -ff RHS_vg
- Remove the physical volume by executing the following command:
# pvremove -ff physical_volume
- If the physical volume (PV) is not created, then create the PV for a RAID 6 volume by executing the following command, else proceed with the next step:
# pvcreate --dataalignment 2560K /dev/vdb
For more information, see the Red Hat Gluster Storage 3.4 Administration Guide: https://access.redhat.com/documentation/en-us/red_hat_gluster_Storage/3.4/html-single/administration_guide/#Formatting_and_Mounting_Bricks. - Create a single volume group from the PV by executing the following command:
# vgcreate volume_group_name disk
For example:# vgcreate RHS_vg /dev/vdb
- Create a thinpool using the following command:
# lvcreate -L size --poolmetadatasize md_size --chunksize chunk_size -T pool_device
For example:# lvcreate -L 2T --poolmetadatasize 16G --chunksize 256 -T /dev/RHS_vg/thin_pool
- Create a thin volume from the pool by executing the following command:
# lvcreate -V size -T pool_device -n thinvol_name
For example:# lvcreate -V 1.5T -T /dev/RHS_vg/thin_pool -n thin_vol
- Create filesystem in the new volume by executing the following command:
# mkfs.xfs -i size=512 thin_vol
For example:# mkfs.xfs -i size=512 /dev/RHS_vg/thin_vol
The back-end is now converted to a thin provisioned volume. - Mount the thin provisioned volume to the brick directory and setup the extended attributes on the bricks. For example:
# setfattr -n trusted.glusterfs.volume-id \ -v 0x$(grep volume-id /var/lib/glusterd/vols/volname/info \ | cut -d= -f2 | sed 's/-//g') $brick
- Disable glusterd.
# systemctl disable glusterd
This prevents it starting during boot time, so that you can ensure the node is healthy before it rejoins the cluster. - Reboot the server.
# shutdown -r now "Shutting down for upgrade to Red Hat Gluster Storage 3.4"
Important
Perform this step only for each thick provisioned volume that has been migrated to thin provisioned volume in the previous step.Change the Automatic File Replication extended attributes from another node, so that the heal process is executed from a brick in the replica subvolume to the thin provisioned brick.- Create a FUSE mount point to edit the extended attributes.
# mount -t glusterfs HOSTNAME_or_IPADDRESS:/VOLNAME /MOUNTDIR
- Create a new directory on the mount point, and ensure that a directory with such a name is not already present.
# mkdir /MOUNTDIR/name-of-nonexistent-dir
- Delete the directory and set the extended attributes.
# rmdir /MOUNTDIR/name-of-nonexistent-dir
# setfattr -n trusted.non-existent-key -v abc /MOUNTDIR # setfattr -x trusted.non-existent-key /MOUNTDIR
- Ensure that the extended attributes of the brick in the replica subvolume is not set to zero.
# getfattr -d -m. -e hex brick_path
In the following example, the extended attributetrusted.afr.repl3-client-1for/dev/RHS_vg/brick2is not set to zero:# getfattr -d -m. -e hex /dev/RHS_vg/brick2 getfattr: Removing leading '/' from absolute path names # file: /dev/RHS_vg/brick2 trusted.afr.dirty=0x000000000000000000000000 trusted.afr.repl3-client-1=0x000000000000000400000002 trusted.gfid=0x00000000000000000000000000000001 trusted.glusterfs.dht=0x000000010000000000000000ffffffff trusted.glusterfs.volume-id=0x924c2e2640d044a687e2c370d58abec9
- Start the
glusterdservice.# systemctl start glusterd
- Verify that you have upgraded to the latest version of Red Hat Gluster Storage.
# gluster --version
- Ensure that all bricks are online.
# gluster volume status
For example:# gluster volume status Status of volume: r2 Gluster process Port Online Pid ------------------------------------------------------------------------------ Brick 10.70.43.198:/brick/r2_0 49152 Y 32259 Brick 10.70.42.237:/brick/r2_1 49152 Y 25266 Brick 10.70.43.148:/brick/r2_2 49154 Y 2857 Brick 10.70.43.198:/brick/r2_3 49153 Y 32270 NFS Server on localhost 2049 Y 25280 Self-heal Daemon on localhost N/A Y 25284 NFS Server on 10.70.43.148 2049 Y 2871 Self-heal Daemon on 10.70.43.148 N/A Y 2875 NFS Server on 10.70.43.198 2049 Y 32284 Self-heal Daemon on 10.70.43.198 N/A Y 32288 Task Status of Volume r2 ------------------------------------------------------------------------------ There are no active volume tasks
- Start self-heal on the volume.
# gluster volume heal volname
- Ensure that self-heal on the volume is complete.
# gluster volume heal volname info
The following example shows a completed self heal operation.# gluster volume heal drvol info Gathering list of entries to be healed on volume drvol has been successful Brick 10.70.37.51:/rhs/brick1/dir1 Number of entries: 0 Brick 10.70.37.78:/rhs/brick1/dir1 Number of entries: 0 Brick 10.70.37.51:/rhs/brick2/dir2 Number of entries: 0 Brick 10.70.37.78:/rhs/brick2/dir2 Number of entries: 0
- Verify that shared storage is mounted.
# mount | grep /run/gluster/shared_storage
- If this node is part of an NFS-Ganesha cluster:
- If the system is managed by SELinux, set the
ganesha_use_fusefsBoolean toon.# setsebool -P ganesha_use_fusefs on
- Start the NFS-Ganesha service.
# systemctl start nfs-ganesha
- Enable and start the cluster.
# pcs cluster enable # pcs cluster start
- Release the node from standby mode.
# pcs cluster unstandby
- Verify that the pcs cluster is running, and that the volume is being exported correctly after upgrade.
# pcs status # showmount -e
NFS-ganesha enters a short grace period after performing these steps. I/O operations halt during this grace period. Wait until you seeNFS Server Now NOT IN GRACEin theganesha.logfile before continuing.
- Optionally, enable the glusterd service to start at boot time.
# systemctl enable glusterd
- Repeat the above steps on the other node of the replica pair. In the case of a distributed-replicate setup, repeat the above steps on all the replica pairs.
- When all nodes have been upgraded, run the following command to update the
op-versionof the cluster. This helps to prevent any compatibility issues within the cluster.# gluster volume set all cluster.op-version 31306
Note
31306is thecluster.op-versionvalue for Red Hat Gluster Storage 3.4 Async Update. Refer to Section 1.5, “Supported Versions of Red Hat Gluster Storage” for the correctcluster.op-versionvalue for other versions.Note
If you want to enable snapshots, see the Red Hat Gluster Storage 3.4 Administration Guide: https://access.redhat.com/documentation/en-us/red_hat_gluster_Storage/3.4/html-single/administration_guide/#Troubleshooting1. - If the client-side quorum was disabled before upgrade, then upgrade it by executing the following command:
# gluster volume set volname cluster.quorum-type auto
- If a dummy node was created earlier, then detach it by executing the following command:
# gluster peer detach <dummy_node name>
- If the geo-replication session between master and slave was disabled before upgrade, then configure the meta volume and restart the session:
# gluster volume set all cluster.enable-shared-storage enable
# gluster volume geo-replication Volume1 example.com::slave-vol config use_meta_volume true
# gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL start
- If you disabled the
disperse.optimistic-change-loganddisperse.eager-lockoptions in order to upgrade an erasure-coded (dispersed) volume, re-enable these settings.# gluster volume set volname disperse.optimistic-change-log on # gluster volume set volname disperse.eager-lock on
7.2.4. Special Consideration for In-Service Software Upgrade
The following sections describe the in-service software upgrade steps for a CTDB setup.
7.2.4.1. In-Service Software Upgrade for a CTDB Setup
Before you upgrade the CTDB packages, ensure you upgrade the Red Hat Gluster Storage server by following these steps. The following steps have to be performed on each node of the replica pair.
- To ensure that the CTDB does not start automatically after a reboot run the following command on each node of the CTDB cluster:
# systemctl disable ctdb
- Stop the CTDB service on the Red Hat Gluster Storage node using the following command on each node of the CTDB cluster:
# systemctl stop ctdb
- To verify if the CTDB and SMB services are stopped, execute the following command:
# ps axf | grep -E '(ctdb|smb|winbind|nmb)[d]'
- Stop the gluster services on the storage server using the following commands:
# systemctl stop glusterd # pkill glusterfs # pkill glusterfsd
- In
/etc/fstab, comment out the line containing the volume used for CTDB service as shown in the following example:# HostName:/volname /gluster/lock glusterfs defaults,transport=tcp 0 0
- Update the server using the following command:
# yum update
- If SELinux support is required, then enable SELinux by following the steps mentioned in, Chapter 10, Enabling SELinux
- After SELinux is enabled, set the following boolean:For Samba
setsebool -P samba_load_libgfapi 1For CTDBsetsebool -P use_fusefs_home_dirs 1 - To ensure the
glusterdservice does not start automatically after reboot, execute the following command:# systemctl disable glusterd
- Reboot the server.
- Update the META=all with the gluster volume information in the following scripts:
/var/lib/glusterd/hooks/1/start/post/S29CTDBsetup.sh /var/lib/glusterd/hooks/1/stop/pre/S29CTDB-teardown.sh
- In
/etc/fstab, uncomment the line containing the volume used for CTDB service as shown in the following example:HostName:/volname /gluster/lock glusterfs defaults,transport=tcp 0 0
- To automatically start the
glusterddaemon every time the system boots, run the following command:# systemctl enable glusterd
- To automatically start the ctdb daemon every time the system boots, run the following command:
# systemctl enable ctdb
- Start the
glusterdservice using the following command:# systemctl start glusterd
- If using NFS to access volumes, enable gluster-NFS using below command:
# gluster volume set <volname> nfs.disable off
For example:# gluster volume set testvol nfs.disable off volume set: success
- Mount the CTDB volume by running the following command:
# mount -a
- Start the CTDB service using the following command:
# systemctl start ctdb
- To verify if CTDB is running successfully, execute the following commands:
# ctdb status # ctdb ip # ctdb ping -n all
CTDB Upgrade
After upgrading the Red Hat Gluster Storage server, upgrade the CTDB package by executing the following steps:
Note
- Upgrading CTDB on all the nodes must be done simultaneously to avoid any data corruption.
- The following steps have to performed only when upgrading CTDB from CTDB 1.x to CTDB 4.x.
- Stop the CTDB service on all the nodes of the CTDB cluster by executing the following command. Ensure it is performed on all the nodes simultaneously as two different versions of CTDB cannot run at the same time in the CTDB cluster:
# systemctl stop ctdb
- Perform the following operations on all the nodes used as samba servers:
- Remove the following soft links:
/etc/sysconfig/ctdb /etc/ctdb/nodes /etc/ctdb/public_addresses
- Copy the following files from the CTDB volume to the corresponding location by executing the following command on each node of the CTDB cluster:
cp /gluster/lock/nodes /etc/ctdb/nodes cp /gluster/lock/public_addresses /etc/ctdb/public_addresses
- Stop and delete the CTDB volume by executing the following commands on one of the nodes of the CTDB cluster:
# gluster volume stop volname
# gluster volume delete volname
- To update CTDB, execute the following command:
# yum update
For more information about configuring CTDB on a Red Hat Gluster Storage server, see section Setting Up CTDB in the Red Hat Gluster Storage Administration Guide
7.2.4.2. Verifying In-Service Software Upgrade
To verify if you have upgraded to the latest version of the Red Hat Gluster Storage server execute the following command:
# gluster --version
7.2.4.3. Upgrading the Native Client
All clients must use the same version of glusterfs-fuse. Red Hat strongly recommends that you upgrade servers before upgrading clients. If you are upgrading from Red Hat Gluster Storage 3.1 Update 2 or earlier, you must upgrade servers and clients simultaneously. For more information regarding upgrading native client, refer to section Upgrading Native Client in the Red Hat Gluster Storage Administration Guide.
