Bug 762333 (GLUSTER-601) - Enable changing 'log-level' of GlusterFS process at runtime
Summary: Enable changing 'log-level' of GlusterFS process at runtime
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-601
Product: GlusterFS
Classification: Community
Component: logging
Version: mainline
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
: GLUSTER-694 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-08 23:51 UTC by Amar Tumballi
Modified: 2015-12-01 16:45 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Amar Tumballi 2010-02-08 23:51:46 UTC 
This feature is very much required for support/debug purposes. Setting up 'TRACE/DEBUG' log-level all the time, the performance of the process may decrease. If we keep the log-level as ERROR, we may miss few logs needed for logging. 

Another issue of init time log-level setting is that, users can't stop/start glusterfs when the error occurs. Hence a mechanism to support run time log-level changes are very important.
Comment 1 Shehjar Tikoo 2010-02-09 07:45:39 UTC 
Use this bug for Pavan's logging infrastructure changes.
Comment 2 Pavan Vilas Sondur 2010-03-23 06:16:24 UTC 
*** Bug 694 has been marked as a duplicate of this bug. ***
Comment 3 Tejas Bhise 2010-08-10 02:47:35 UTC 
Amar - since you/shishir are going to take this up ...
Comment 4 Anand Avati 2010-08-12 04:45:51 UTC 
PATCH: http://patches.gluster.com/patch/4081 in master (logging enhancements)
Note You need to log in before you can comment on or make changes to this bug.