Bug 1121018

Summary: [FEAT] : provide an option to set glusterd log levels other than command line flag
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: spandura
Component: glusterdAssignee: Atin Mukherjee <amukherj>
Status: CLOSED WONTFIX QA Contact: storage-qa-internal <storage-qa-internal>
Severity: medium Docs Contact:
Priority: low    
Version: rhgs-3.0CC: amukherj, gyadav, nlevinki, spandura, vbellur
Target Milestone: ---Keywords: FutureFeature, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
: 1123294 (view as bug list) Environment:
Last Closed: 2017-08-11 09:58:16 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: 1123294    

Description spandura 2014-07-18 07:45:55 UTC
Description of problem:
======================
It would be really helpful for debugging any issues related to glusterd if we can set the log level of glusterd using a command rather than restarting the glusterd with "DEBUG" option. If we restart the glusterd, we might not hit the issue after restart as we lose the current state of glusterd. . Hence it would be really helpful to have a option to set the glusterd log levels. 

For example: https://bugzilla.redhat.com/show_bug.cgi?id=1121015 doesn't have enough information in the glusterd logs on why the command failed. The developer wants more information but we are get the information without restarting glusterd.  

Version-Release number of selected component (if applicable):
============================================================
glusterfs 3.6.0.24 built on Jul  3 2014 11:03:38

Comment 2 Atin Mukherjee 2014-07-22 06:29:41 UTC
Are you looking at a command to set a specific log level per glusterd or cli command should set the log level of glusterd across the cluster?

Comment 6 Red Hat Bugzilla 2023-09-14 02:11:42 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days