Description of problem: As of now, gluster volume get <volname> cluster.op-version can provide the current op-version with what cluster is running with, however users may want to know at what max value they can bump up the op-version given auto op-version update doesn't happen on an upgrade and users may be running the cluster with a very old op-version. The implementation can consider all the max-op-version values from all the nodes and come up with the lowest number which could be the max supported version. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/15463 (cli, glusterd: New CLI command to get maximum supported op-version) posted (#1) for review on master by Samikshan Bairagya (samikshan)
REVIEW: http://review.gluster.org/16283 (glusterd: Get maximum supported op-version in a cluster) posted (#1) for review on master by Samikshan Bairagya (samikshan)
REVIEW: http://review.gluster.org/16283 (glusterd: Get maximum supported op-version in a cluster) posted (#2) for review on master by Samikshan Bairagya (samikshan)
REVIEW: http://review.gluster.org/16283 (glusterd: Get maximum supported op-version in a cluster) posted (#3) for review on master by Samikshan Bairagya (samikshan)
REVIEW: http://review.gluster.org/16283 (glusterd: Get maximum supported op-version in a cluster) posted (#4) for review on master by Samikshan Bairagya (samikshan)
COMMIT: http://review.gluster.org/16283 committed in master by Atin Mukherjee (amukherj) ------ commit 76fbeafbf56a61768c81f622b354e3c95a00e986 Author: Samikshan Bairagya <samikshan> Date: Mon Dec 19 15:07:14 2016 +0530 glusterd: Get maximum supported op-version in a cluster gluster volume get <VOLNAME> cluster.opversion gives us the current op-version on which the cluster is operating. There is no command that lets the user know the maximum supported op-version that the cluster can run on. This patch adds a new global option cluster.max-op-version, that can be used to retrieve the maximum supported op-version in a cluster. Usage: # gluster volume get all cluster.max-op-version Example output: Option Value ------ ----- cluster.max-op-version 30900 NOTE: The only way to test this feature for now is to set the GD_OP_VERSION_MAX macro to different values (30800 for 3.8,30900 for 3.9, and so on) and rebuild glusterd. Since the regression test framework currently doesn't have support to simulate these tests, there are no accompanying regression tests for this feature. It should be possible to add tests once glusto comes in and makes it easier to run a heterogeneous cluster. Change-Id: I547480ee5e7912664784643e436feb198b6d16d0 BUG: 1365822 Signed-off-by: Samikshan Bairagya <samikshan> Reviewed-on: http://review.gluster.org/16283 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Atin Mukherjee <amukherj>
REVIEW: http://review.gluster.org/16447 (glusterd: Get maximum supported op-version in a cluster) posted (#1) for review on release-3.10 by Kaleb KEITHLEY (kkeithle)
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.0, please open a new bug report. glusterfs-3.10.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/gluster-users/2017-February/030119.html [2] https://www.gluster.org/pipermail/gluster-users/