Bug 1597509

Summary: introduce cluster.daemon-log-level option
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Atin Mukherjee <amukherj>
Component: glusterdAssignee: Atin Mukherjee <amukherj>
Status: CLOSED ERRATA QA Contact: Nag Pavan Chilakam <nchilaka>
Severity: urgent Docs Contact:
Priority: urgent    
Version: rhgs-3.3CC: amukherj, nchilaka, nigoyal, rhinduja, rhs-bugs, sankarshan, sheggodu, srakonde, storage-qa-internal, vbellur
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.3.1 Async   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.8.4-54.15 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1597473
: 1597511 (view as bug list) Environment:
Last Closed: 2018-07-19 06:00:07 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: 1597473    
Bug Blocks: 1597511    

Description Atin Mukherjee 2018-07-03 06:15:17 UTC 
+++ This bug was initially created as a clone of Bug #1597473 +++

Description of problem:

As of now we have a client-log-level option which can be applied per volume basis. However this gets applied on all the clients and is not an global option. In a scaled setup where there are too many new volume requests coming in, daemons like shd get restarted on every volume start which can bloat the shd logs significantly. Users might need a global tuning which can help in logging in a particular log level for all the node level daemon services (excluding bricks).

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Worker Ant on 2018-07-02 22:29:21 EDT ---

REVIEW: https://review.gluster.org/20442 (glusterd: Introduce daemon-log-level cluster wide option) posted (#2) for review on master by Atin Mukherjee
Comment 25 errata-xmlrpc 2018-07-19 06:00:07 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:2222