Bug 761811 (GLUSTER-79) - Log message cleanup
Summary: Log message cleanup
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-79
Product: GlusterFS
Classification: Community
Component: logging
Version: pre-2.0
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Vikas Gorur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-25 11:26 UTC by Basavanagowda Kanur
Modified: 2009-08-20 07:39 UTC (History)
2 users (show)

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


Attachments (Terms of Use)

Description Basavanagowda Kanur 2009-06-25 11:26:20 UTC
[Migrated from RT] - ticket 899 [http://support.gluster.com/rt/Ticket/Display.html?id=899]

Wed Apr 08 04:47:11 2009  	 guru - Ticket created  	 	 

Version: glusterfs 2.0.0 pre35

1)
2009-04-07 05:54:33 N [client-protocol.c:6169:client_setvolume_cbk]
brick8-tcp: connection and handshake succeeded

User does not care if there is a handshake involved at all. The next
message is sufficient:



2)
2009-04-07 05:54:33 N [afr.c:2016:notify] afr8: subvolume brick1-tcp came up

"subvolume <name> 'connected'" is probably a better phrase

--------------------------------------------------------------------------------
#   	Thu Apr 09 21:51:54 2009 	amar - Correspondence added

On Wed Apr 08 04:47:11 2009, guru wrote:
> 1)
> 2009-04-07 05:54:33 N [client-protocol.c:6169:client_setvolume_cbk]
> brick8-tcp: connection and handshake succeeded
>
> User does not care if there is a handshake involved at all. The next
> message is sufficient:
>
>
If you prefer 'next' msg, it has to be in 'client-protocol itself, not
in AFR.
>
> 2)
> 2009-04-07 05:54:33 N [afr.c:2016:notify] afr8: subvolume brick1-tcp
came up
>
> "subvolume <name> 'connected'" is probably a better phrase



-- 
Amar Tumballi

Comment 1 Vikas Gorur 2009-07-09 10:56:37 UTC
Fixed in release 2.0 and later. Commits a76ce13ce29249f4622fcfef39bcd087c1cd050a and 7bbbc9c8786d079055138ac4f8ea98b576c73ce0.


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