Bug 763698 (GLUSTER-1966) - Unnecessarily verbose logs at the default log level
Summary: Unnecessarily verbose logs at the default log level
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-1966
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.1.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-15 23:36 UTC by Vikas Gorur
Modified: 2015-12-01 16:45 UTC (History)
3 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 Vikas Gorur 2010-10-15 23:36:49 UTC 
The glusterd log has messages such as:

[2010-10-15 16:23:07.740393] I [glusterd-op-sm.c:5061:glusterd_op_sm_inject_even
t] glusterd: Enqueuing event: 'GD_OP_EVENT_ALL_ACC'
[2010-10-15 16:23:07.740403] I [glusterd-op-sm.c:4740:glusterd_op_sm_transition_
state] : Transitioning from 'Unlock sent' to 'Unlock sent' due to event 'GD_OP_E
VENT_RCVD_ACC'
[2010-10-15 16:23:07.740412] I [glusterd-op-sm.c:5109:glusterd_op_sm] : Dequeued
 event of type: 'GD_OP_EVENT_ALL_ACC'
[2010-10-15 16:23:07.740423] I [glusterd-op-sm.c:4561:glusterd_op_txn_complete] 
glusterd: Cleared local lock
[2010-10-15 16:23:07.740458] I [glusterd-op-sm.c:4740:glusterd_op_sm_transition_
state] : Transitioning from 'Unlock sent' to 'Default' due to event 'GD_OP_EVENT
_ALL_ACC'

These make no sense to a user, and should not be logged under the default log level. These messages are more appropriate at the DEBUG or TRACE level.
Comment 1 Anand Avati 2010-10-29 07:42:21 UTC 
PATCH: http://patches.gluster.com/patch/5601 in master (cli,mgmt/glusterd: fsm log implementation)
Comment 2 Pranith Kumar K 2010-11-09 06:02:36 UTC 
implemented hidden commands fsm log [<peer-name>] and marked these logs to DEBUG level to fix the issue
Note You need to log in before you can comment on or make changes to this bug.