gluster/glusterdocs
1
0
Fork 0
mirror of https://github.com/gluster/glusterdocs.git synced 2026-02-05 15:47:01 +01:00
Code Issues Releases Activity

Added a note for quota in upgrade procedure (#610)

Browse Source 
Added a note about how to fix the issue caused by the change
in checksum computation while upgrading from a version less than 7.0

Signed-off-by: nik-redhat <nladha@redhat.com>
This commit is contained in:
Nikhil Ladha
2020-11-03 12:09:39 +05:30
committed by GitHub
parent b9a1750755
commit 6b120c4571
2 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/Upgrade-Guide/Generic_Upgrade_procedure.md
View File

@@ -115,6 +115,14 @@ Perform the following steps post upgrading the entire trusted storage pool,
- Proceed to [upgrade the clients](#upgrade-procedure-for-clients) to new-version version as well
- Post upgrading the clients, for replicate volumes, it is recommended to enable the option `gluster volume set <volname> fips-mode-rchecksum on` to turn off usage of MD5 checksums during healing. This enables running Gluster on FIPS compliant systems.
#### If upgrading from a version lesser than Gluster 7.0
> **NOTE:** If you have ever enabled quota on your volumes then after the upgrade
is done, you will have to restart all the nodes in the cluster one by one so as to
fix the checksum values in the quota.cksum file under the `/var/lib/glusterd/vols/<volname>/ directory.`
The peers may go into `Peer rejected` state while doing so but once all the nodes are rebooted
everything will be back to normal.
### Upgrade procedure for clients
Following are the steps to upgrade clients to the new-version version,

6
docs/Upgrade-Guide/upgrade_to_7.md
View File

@@ -9,6 +9,12 @@ Refer, to the [Upgrading to 4.1](./upgrade_to_4.1.md) guide and follow
documented instructions, replacing 7 when you encounter 4.1 in the guide as the
version reference.
> **NOTE:** If you have ever enabled quota on your volumes then after the upgrade
is done, you will have to restart all the nodes in the cluster one by one so as to
fix the checksum values in the quota.cksum file under the `/var/lib/glusterd/vols/<volname>/ directory.`
The peers may go into `Peer rejected` state while doing so but once all the nodes are rebooted
everything will be back to normal.
### Major issues
1. The following options are removed from the code base and require to be unset