Bug 235697 - GFS2 requires a minimum lock hold time for glocks
GFS2 requires a minimum lock hold time for glocks
Status: CLOSED DUPLICATE of bug 248480
Product: Fedora
Classification: Fedora
Component: GFS-kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Steve Whitehouse
: FutureFeature
Depends On:
Blocks: 236404
  Show dependency treegraph
Reported: 2007-04-09 13:56 EDT by Steve Whitehouse
Modified: 2007-11-30 17:12 EST (History)
2 users (show)

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

Attachments (Terms of Use)

  None (edit)
Description Steve Whitehouse 2007-04-09 13:56:40 EDT
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 Steve Whitehouse 2007-08-25 09:42:41 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.