Bug 236404 – GFS2 requires a minimum lock hold time for glocks

Bug 236404 - GFS2 requires a minimum lock hold time for glocks

Summary:	GFS2 requires a minimum lock hold time for glocks

Status:	CLOSED DUPLICATE of bug 248480

Aliases:	None

Product:	Red Hat Enterprise Linux 5
Classification:	Red Hat
Component:	kernel (Show other bugs)
Sub Component:
Version:	5.2
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Steve Whitehouse
QA Contact:	Dean Jansa
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature

Depends On:	235697
Blocks:
	Show dependency tree / graph

Reported:	2007-04-13 12:33 EDT by Nate Straz
Modified:	2009-05-27 23:34 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-08-25 09:43:39 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Nate Straz 2007-04-13 12:33:21 EDT

+++ 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 Product and Program Management 2007-04-13 14:04:08 EDT

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 09:06:56 EDT

This has missed 5.1, so retarget for 5.2?

Comment 3 Steve Whitehouse 2007-08-25 09:43:39 EDT


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

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