Bug 491129

Summary:	low values of --cluster-read-max value unstable for large numbers of concurrent connection closures
Product:	Red Hat Enterprise MRG	Reporter:	Gordon Sim <gsim>
Component:	Release_Notes	Assignee:	Lana Brindley <lbrindle>
Status:	CLOSED CURRENTRELEASE	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	medium	Docs Contact:
Priority:	urgent
Version:	Development	CC:	mhideo
Target Milestone:	1.1.1	Keywords:	Documentation
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-03-23 04:13:29 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gordon Sim 2009-03-19 15:00:49 UTC

The cluster module offers an experimental tuning option, --cluster-read-max. Users are advised not to use this option as low values have been observed to cause the broker to crash when a large number of connections are closed simultaneously. The default value of this setting is advised and no value below 3 should be used.

Comment 1 Lana Brindley 2009-03-23 04:13:29 UTC

<row>
	<entry>
		491129
	</entry>
	<entry>
		The cluster module offers an experimental tuning option, <command>--cluster-read-max</command>. Low values for this option can cause the broker to shutdown when a large number of connections are closed simultaneously. This setting should not be below 3 in order to avoid this issue.
	</entry>
</row>

Will be on the stage shortly.

LKB