Bug 1597509 - introduce cluster.daemon-log-level option
Summary: introduce cluster.daemon-log-level option
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: RHGS 3.3.1 Async
Assignee: Atin Mukherjee
QA Contact: Nag Pavan Chilakam
URL:
Whiteboard:
Depends On: 1597473
Blocks: 1597511
TreeView+ depends on / blocked
 
Reported: 2018-07-03 06:15 UTC by Atin Mukherjee
Modified: 2018-07-19 06:01 UTC (History)
10 users (show)

Fixed In Version: glusterfs-3.8.4-54.15
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1597473
: 1597511 (view as bug list)
Environment:
Last Closed: 2018-07-19 06:00:07 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2222 0 None None None 2018-07-19 06:01:41 UTC

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


Note You need to log in before you can comment on or make changes to this bug.