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

Bug 1640495

Summary:	[GSS] Fix log level issue with brick mux
Product:	[Community] GlusterFS	Reporter:	Mohit Agrawal <moagrawa>
Component:	core	Assignee:	Mohit Agrawal <moagrawa>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	abhishku, amukherj, atumball, bkunal, madam, nravinas, rhinduja, rhs-bugs, sankarshan, sheggodu, storage-qa-internal
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	brick-multiplexing
Fixed In Version:	glusterfs-6.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1598407	Environment:
Last Closed:	2019-03-25 16:31:24 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:	1598407
Bug Blocks:

Comment 1 Mohit Agrawal 2018-10-18 08:51:47 UTC

Hi, 

RCA: A log-level option is automatically enabled for other volumes
because log-level saved in glusterfsd_ctx and ctx is common for volumes
those are attached with same brick. To resolve it set log level for all children xlator's at the time of the graph reconfigure at io-stat xlator.

For server_xlator we can't avoid the logs for other volumes while log are enabled only for a single volume because server_xlator is common for all brick xlators.

Patch is posted to resolve the same
https://review.gluster.org/#/c/glusterfs/+/20488/

Thanks,
Mohit Agrawal

Comment 2 Worker Ant 2018-10-24 06:30:13 UTC

COMMIT: https://review.gluster.org/20488 committed in master by "Amar Tumballi" <amarts> with a commit message- glusterfs: During reconfigure set log-level per xlator level

Problem: In brick_mux environment, while a user has enabled brick-log-level
         for anyone volume, it automatically enables for other volumes
         also those are attached with same brick.

Solution: A log-level option is automatically enabled for other volumes
          because log-level saved in glusterfsd_ctx and ctx is common for
          volumes those are attached with same brick. To resolve it
          set log level for all children xlator's at the time of the graph
          reconfigure at io-stat xlator.

Change-Id: Id9a6efa05d286e0bea2d47f49292d084e7bb2fcf
fixes: bz#1640495
Signed-off-by: Mohit Agrawal <moagrawal>

Comment 3 Shyamsundar 2019-03-25 16:31:24 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/