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

Bug 1597247

Summary:	restart all the daemons after all the bricks
Product:	[Community] GlusterFS	Reporter:	Atin Mukherjee <amukherj>
Component:	glusterd	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-5.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-23 15:12:23 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:

Description Atin Mukherjee 2018-07-02 11:22:06 UTC

Description of problem:

In a scaled environment having a large number of volumes when a node or a gluster pod gets restarted, glustershd logs grow unnecessarily because of every restart of bricks in the volume the daemons get restarted which probably can be avoided.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2018-07-02 11:25:53 UTC

REVIEW: https://review.gluster.org/20439 (glusterd: Don't restart daemon services at every brick restart) posted (#1) for review on master by Atin Mukherjee

Comment 2 Atin Mukherjee 2018-07-02 12:26:15 UTC

(In reply to Atin Mukherjee from comment #0)
> Description of problem:
> 
> In a scaled environment having a large number of volumes when a node or a
> gluster pod gets restarted, glustershd logs grow unnecessarily because of
> every restart of bricks in the volume the daemons get restarted which
> probably can be avoided.

Please ignore the above description as I realize that the current code already handles this part but in not a cleaned manner. We need to restart the daemon at the end of starting all the bricks, not in between.

> 
> 
> Version-Release number of selected component (if applicable):
> 
> 
> How reproducible:
> 
> 
> Steps to Reproduce:
> 1.
> 2.
> 3.
> 
> Actual results:
> 
> 
> Expected results:
> 
> 
> Additional info:

Comment 3 Worker Ant 2018-07-03 13:48:41 UTC

COMMIT: https://review.gluster.org/20439 committed in master by "Atin Mukherjee" <amukherj> with a commit message- glusterd: start the services after all the bricks are up

glusterd_svcs_manager () should be called post starting all the volumes
at one go.

Change-Id: I838cc50c29f3930a483aa9671958cdc186904030
Fixes: bz#1597247
Signed-off-by: Atin Mukherjee <amukherj>

Comment 4 Shyamsundar 2018-10-23 15:12:23 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-5.0, please open a new bug report.

glusterfs-5.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/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/