8.3. In-service Software Update to Red Hat Gluster Storage 3.1.x from 3.y.z

Important

In-service software update includes minor bug fixes and enhancements. You can update your system from Red Hat Gluster Storage 3.0.x to 3.1.y or from 3.1.x to 3.1.y.

To update your system to Red Hat Gluster Storage 3.1.x, follow these steps. The following steps must be performed on each node of the replica pair:

Note

NFS-Ganesha does not support in-service update, hence all the running services and IO's have to be stopped before starting the update process. For more information see, Section 8.2, “Updating NFS-Ganesha in the Offline Mode”.
Ensure that the system is registered to the Red Hat Network. For more information refer to, Section 2.6, “Subscribing to the Red Hat Gluster Storage Server Channels”
Updating Red Hat Gluster Storage using ISO can be performed only from the previous release. This means that upgrading to Red Hat Gluster Storage 3.1 using ISO can only be done from Red Hat Gluster Storage 3.0 Update 4. For a complete list of supported Red Hat Gluster Storage releases, see Section 1.5, “Supported Versions of Red Hat Gluster Storage”.
Ensure not to perform any volume operations while the cluster is getting updated.

Warning

While Red Hat Gluster Storage supports in-service upgrades, the SMB and CTDB services do not. The procedure outlined in this section does involve service interruptions to the SMB and CTDB services.
Samba version 3 is being deprecated from Red Hat Gluster Storage 3.0 Update 4. Further updates will not be provided for samba-3.x. It is recommended that you upgrade to Samba-4.x, which is provided in a separate channel or repository, for all updates including the security updates.
Downgrading Samba from Samba 4.x to Samba 3.x is not supported.
Ensure that Samba is upgraded on all the nodes simultaneously, as running different versions of Samba in the same cluster will lead to data corruption.

Stop the gluster services on the storage server using the following commands:
```
service glusterd stop
pkill glusterfs
pkill glusterfsd
```
```
# service glusterd stop 
# pkill glusterfs 
# pkill glusterfsd
```
Copy to Clipboard Toggle word wrap
1. For Red Hat Gluster Storage 3.0.4 or later on Red Hat Enterprise Linux 6.7, if you require Samba, then enable the following repository:
  # subscription-manager repos --enable=rh-gluster-3-samba-for-rhel-6-server-rpms
  Copy to Clipboard Toggle word wrap
2. Stop the CTDB and SMB services across all nodes in the Samba cluster using the following command. This is because different versions of Samba cannot run in the same Samba cluster.
  # service ctdb stop
  Copy to Clipboard Toggle word wrap
  Stopping the CTDB service also stops the SMB service.
3. To verify if the CTDB and SMB services are stopped, execute the following command:
  ps axf | grep -E '(ctdb|smb|winbind|nmb)[d]'
  Copy to Clipboard Toggle word wrap
Update the server using the following command:
```
yum update
```
```
# yum update
```
Copy to Clipboard Toggle word wrap
Reboot the server if a kernel update was included as part of the update process in the previous step.
Note
If a reboot of the server was not required, then start the gluster services on the storage server using the following command:
# service glusterd start
Copy to Clipboard Toggle word wrap
1. If the CTDB and SMB services were stopped earlier, then start the services by executing the following command.
  
  # service ctdb start
  
  Copy to Clipboard Toggle word wrap
2. To verify if the CTDB and SMB services have started, execute the following command:
  
  ps axf | grep -E '(ctdb|smb|winbind|nmb)[d]'
  
  Copy to Clipboard Toggle word wrap
Start self-heal on the volume.
```
gluster volume heal volname
```
```
# gluster volume heal volname
```
Copy to Clipboard Toggle word wrap
To verify if you have upgraded to the latest version of the Red Hat Gluster Storage server execute the following command:
```
gluster --version
```
```
# gluster --version
```
Copy to Clipboard Toggle word wrap
Ensure that all the bricks are online. To check the status, execute the following command:
```
gluster volume status
```
```
# gluster volume status
```
Copy to Clipboard Toggle word wrap
Ensure self-heal is complete on the replica using the following command:
```
gluster volume heal volname info
```
```
# gluster volume heal volname info
```
Copy to Clipboard Toggle word wrap
Repeat the above steps on the other node of the replica pair.
Note
In the case of a distributed-replicated setup, repeat the above steps on all replica pairs.
When all nodes have been upgraded, run the following command to update the op-version of the cluster. This helps to prevent any compatibility issues within the cluster.
```
gluster volume set all cluster.op-version 30707
```
```
# gluster volume set all cluster.op-version 30707
```
Copy to Clipboard Toggle word wrap

返回顶部

此内容没有您所选择的语言版本。

8.3. In-service Software Update to Red Hat Gluster Storage 3.1.x from 3.y.z

学习

尝试、购买和销售

社区

关于红帽文档

让开源更具包容性

關於紅帽

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links