7.3. In-service Software Update from Red Hat Gluster Storage
- You must update all Red Hat Gluster Storage servers before updating any clients.
- If geo-replication is in use, slave nodes must be updated before master nodes.
- NFS-Ganesha does not support in-service updates. All the running services and I/O operations must be stopped before starting the update process. For more information see, Section 7.2.2, “Updating NFS-Ganesha in the Offline Mode”.
- Dispersed volumes (volumes that use erasure coding) do not support in-service updates and cannot be updated in a non-disruptive manner.
- The SMB and CTDB services do not support in-service updates. The procedure outlined in this section involves service interruptions to the SMB and CTDB services.
- If updating Samba, ensure that Samba is upgraded on all nodes simultaneously, as running different versions of Samba in the same cluster results in data corruption.
- Your system must be registered to Red Hat Network. For more information refer to Section 2.6, “Subscribing to the Red Hat Gluster Storage Server Channels”
- Do not perform any volume operations while the cluster is being updated.
Updating Red Hat Gluster Storage 3.2 in in-service mode
- If you have a replicated configuration, perform these steps on all nodes of a replica set.If you have a distributed-replicated setup, perform these steps on one replica set at a time, for all replica sets.
- Stop any geo-replication sessions.
# gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL stop
- Verify that there are no pending self-heals:
# gluster volume heal volname infoWait for any self-heal operations to complete before continuing.
- Stop the gluster services on the storage server using the following commands:
# service glusterd stop # pkill glusterfs # pkill glusterfsd
- If you use Samba:
- Enable the required repository.On Red Hat Enterprise Linux 6.7 or later:
# subscription-manager repos --enable=rh-gluster-3-samba-for-rhel-6-server-rpmsOn Red Hat Enterprise Linux 7:
# subscription-manager repos --enable=rh-gluster-3-samba-for-rhel-7-server-rpms
- Stop the CTDB and SMB services across all nodes in the Samba cluster using the following command. Stopping the CTDB service also stops the SMB service.
# service ctdb stopThis ensures different versions of Samba do not run in the same Samba cluster.
- Verify that the CTDB and SMB services are stopped by running the following command:
ps axf | grep -E '(ctdb|smb|winbind|nmb)[d]'
- Update the server using the following command:
# yum updateWait for the update to complete.
- If a kernel update was included as part of the update process in the previous step, reboot the server.
- If a reboot of the server was not required, then start the gluster services on the storage server using the following command:
# service glusterd startAdditionally, if you use Samba:
/gluster/lockbefore starting CTDB by executing the following command:
# mount -a
- If the CTDB and SMB services were stopped earlier, then start the services by executing the following command.
# service ctdb start
- To verify if the CTDB and SMB services have started, execute the following command:
ps axf | grep -E '(ctdb|smb|winbind|nmb)[d]'
- To verify that you have updated to the latest version of the Red Hat Gluster Storage server execute the following command and compare output with the desired version in Section 1.5, “Supported Versions of Red Hat Gluster Storage”.
# gluster --version
- Ensure that all bricks are online. To check the status, execute the following command:
# gluster volume status
- Start self-heal on the volume.
# gluster volume heal volname
- Ensure self-heal is complete on the replica using the following command:
# gluster volume heal volname info
- When all nodes in the volume 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 31001
cluster.op-versionvalue for Red Hat Gluster Storage 3.2.0. Refer to Section 1.5, “Supported Versions of Red Hat Gluster Storage” for the correct
cluster.op-versionvalue for other versions.
- If you had a meta volume configured prior to this upgrade, and you did not reboot as part of the upgrade process, mount the meta volume:
# mount /var/run/gluster/shared_storage/If this command does not work, review the content of
/etc/fstaband ensure that the entry for the shared storage is configured correctly and re-run the
mountcommand. The line for the meta volume in the
/etc/fstabfile should look like the following:
hostname:/gluster_shared_storage /var/run/gluster/shared_storage/ glusterfs defaults 0 0
- If you use geo-replication, restart geo-replication sessions when upgrade is complete.
# gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL start
NoteAs a result of BZ#1347625, you may need to use the
forceparameter to successfully restart in some circumstances.
# gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL start force