Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1648237

Summary:	Bumping up of op-version times out on a scaled system with ~1200 volumes
Product:	[Community] GlusterFS	Reporter:	Atin Mukherjee <amukherj>
Component:	glusterd	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	high
Version:	mainline	CC:	abhishku, bmekala, bugs, kramdoss, rhs-bugs, sankarshan, storage-qa-internal, vbellur
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1648210	Environment:
Last Closed:	2019-03-25 16:31:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1648210
Bug Blocks:

Comment 1 Atin Mukherjee 2018-11-09 08:19:19 UTC

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

Comment 2 Worker Ant 2018-11-09 08:21:25 UTC

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

Comment 3 Worker Ant 2018-11-12 03:41:12 UTC

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

Comment 4 Shyamsundar 2019-03-25 16:31:51 UTC

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/