Bug 762098 (GLUSTER-366)

Summary:	Infinite loop with centralized logging.
Product:	[Community] GlusterFS	Reporter:	Harshavardhana <fharshav>
Component:	logging	Assignee:	Harshavardhana <fharshav>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	mainline	CC:	cww, gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Harshavardhana 2009-11-09 18:53:46 UTC

Centralized logging is not really a need as Gluster Storage Platform addresses
this issue. Making a single server choke, when there are like 1000-2000 clients
is a bad idea. 


While the issue was reproduced and seen to be that "client_log_cbk" was not
even the list of mops, so "cbks" first element over lapped ie. client_forget_cbk


Now there needs two fixes

1. Disable the centralized logging. 
2. Added boundaries for "gf_mops, gf_ops, gf_cbks" to avoid
   future overlapping.

Comment 1 Harshavardhana 2009-11-09 21:50:45 UTC

While testing glusterfs 3.0.0pre1 version observed an infinite loop of 
logging which occurs on the client side with messages logged for 
'client_forget_cbk'

Comment 2 Anand Avati 2009-11-13 14:33:16 UTC

PATCH: http://patches.gluster.com/patch/2186 in master (Disabled centralized logging by default.)

Comment 3 Anand Avati 2009-11-26 07:48:50 UTC

PATCH: http://patches.gluster.com/patch/2363 in master (Added boundaries for each fops, mops and cbks.)