Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 236404

Summary:	GFS2 requires a minimum lock hold time for glocks
Product:	Red Hat Enterprise Linux 5	Reporter:	Nate Straz <nstraz>
Component:	kernel	Assignee:	Steve Whitehouse <swhiteho>
Status:	CLOSED DUPLICATE	QA Contact:	Dean Jansa <djansa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.2	CC:	adas, cluster-maint, nobody+wcheng
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-08-25 13:43:39 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:
Bug Depends On:	235697
Bug Blocks:

Description Nate Straz 2007-04-13 16:33:21 UTC

+++ This bug was initially created as a clone of Bug #235697 +++

To solve the performance problems seen with the alternate test and similar
contention cases, we need to implement some kind of minimum lock hold time to
ensure that the cluster makes progress even in heavy lock traffic.

Probably we need a user configurable, but with a sensible default, setting which
puts a maximum cap on the minimum lock hold time, and then try to set the lock
hold time automatically using information gathered from the system, such as how
long the wait has been when acquiring the lock, how much work needs to be done, etc.

Comment 1 RHEL Program Management 2007-04-13 18:04:08 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 2 Steve Whitehouse 2007-06-05 13:06:56 UTC

This has missed 5.1, so retarget for 5.2?

Comment 3 Steve Whitehouse 2007-08-25 13:43:39 UTC


*** This bug has been marked as a duplicate of 248480 ***