Description of problem: While trying to bump up the op-version after upgrading a CNS setup from 3.9 to 3.10, the operation timed out. sh-4.2# gluster volume set all cluster.op-version 31302 Error : Request timed out However, after few minutes the op-version had got bumped up. So, there is no functionality impact on the command getting timed out. sh-4.2# gluster vol get all all Option Value ------ ----- cluster.server-quorum-ratio 51 cluster.enable-shared-storage disable cluster.op-version 31302 cluster.max-op-version 31302 cluster.brick-multiplex on cluster.max-bricks-per-process 0 cluster.daemon-log-level INFO Version-Release number of selected component (if applicable): mainline How reproducible: Always Steps to Reproduce: 1. create a CNS system with 1200 volumes 2. upgrade CNS 3.9 to to OCS 3.10 3. After the upgrade, bump up the op-version by running 'gluster volume set all cluster.op-version 31302' Actual results: command timed out
REVIEW: https://review.gluster.org/21608 (glusterd: don't call svcs_reconfigure for all volumes during op-version bump up) posted (#1) for review on master by Atin Mukherjee
REVIEW: https://review.gluster.org/21608 (glusterd: don't call svcs_reconfigure for all volumes during op-version bump up) posted (#3) for review on master by Amar Tumballi
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-6.0, please open a new bug report. glusterfs-6.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] https://lists.gluster.org/pipermail/announce/2019-March/000120.html [2] https://www.gluster.org/pipermail/gluster-users/