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

Add more details on retrieving client op-version information

Browse Source
This commit is contained in:
Samikshan Bairagya
2017-02-23 15:02:42 +05:30
parent 9742974343
commit b401a4e194
1 changed files with 10 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
Upgrade-Guide/op_version.md
View File

@@ -12,10 +12,12 @@ Current op-version can be queried as below:
[root@~]#gluster volume get all cluster.op-version
To check maximum op-version supported by the cluster, the following query can be used:
To get the maximum possible op-version a cluster can support, the following query can be used:
[root@~]#gluster volume get all cluster.max-op-version
For example, if some nodes in a cluster have been upgraded to X and some to X+, then the maximum op-version supported by the cluster is X, and the cluster.op-version can be bumped up to X to support new features.
op-version can be updated as below.
For example, after upgrading to glusterfs-3.7.1, set op-version as:
@@ -26,7 +28,13 @@ This is not mandatory, but advisable to have updated op-version if you want to m
###Client op-version
To check op-version information for clients the following query can be used:
When trying to set a volume option, it might happen that one or more of the connected clients cannot support the feature being set and might need to be upgraded to the op-version the cluster is currently running on.
To check op-version information for the connected clients and find the offending client, the following query can be used:
[root@~]#gluster volume status <all|VOLNAME> clients
The respective clients can then be upgraded to the required version.
This information could also be used to make an informed decision while bumping up the op-version of a cluster, so that connected clients can support all the new features provided by the upgraded cluster as well.