Bug 1539510

Summary:	Optimize glusterd_import_friend_volume code path
Product:	[Community] GlusterFS	Reporter:	Atin Mukherjee <amukherj>
Component:	glusterd	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-v4.1.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1540554 1543709 (view as bug list)		Environment:
Last Closed:	2018-06-20 17:58:44 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:
Bug Blocks:	1540554, 1543709

Description Atin Mukherjee 2018-01-29 04:58:30 UTC

Description of problem:

When glusterd restarts and in case there's a version mismatch detected for one of the volumes, glusterd was ending up with updating all the volumes which is a
overkill.

Version-Release number of selected component (if applicable):
mainline

How reproducible:
Always

Comment 1 Worker Ant 2018-01-29 05:00:30 UTC

REVIEW: https://review.gluster.org/19358 (glusterd: optimize glusterd import volumes code path) posted (#1) for review on master by Atin Mukherjee

Comment 2 Worker Ant 2018-01-31 09:12:50 UTC

COMMIT: https://review.gluster.org/19358 committed in master by "Amar Tumballi" <amarts> with a commit message- glusterd: optimize glusterd import volumes code path

In case there's a version mismatch detected for one of the volumes
glusterd was ending up with updating all the volumes which is a
overkill.

Change-Id: I6df792db391ce3a1697cfa9260f7dbc3f59aa62d
BUG: 1539510
Signed-off-by: Atin Mukherjee <amukherj>

Comment 3 Shyamsundar 2018-06-20 17:58:44 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-v4.1.0, please open a new bug report.

glusterfs-v4.1.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/announce/2018-June/000102.html
[2] https://www.gluster.org/pipermail/gluster-users/