Bug 460051 - yum lock should be fair in face of concurrent waiters
yum lock should be fair in face of concurrent waiters
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Seth Vidal
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-08-25 15:27 EDT by Frank Ch. Eigler
Modified: 2014-01-21 18:06 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-08-25 15:42:21 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 Frank Ch. Eigler 2008-08-25 15:27:57 EDT
Description of problem:
When starting several yum jobs in parallel, starvation can occur.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Run a "yum" job in a shell script loop.
2. Also run a yum job by hand in a separate window.
Actual results:
Observe that the shell loop will nearly always hold on to the yum lock, starving the separate one.

Expected results:
Yum locks should be more fair, so a yum job waiting for a long time should
get priority over one that is freshly started.
Comment 1 Seth Vidal 2008-08-25 15:42:21 EDT
there's no internal communication between yum processes. They're just watching a lock file and checking back. The one that checks most recently after the last lock owner exits will get it.

I'm closing this cantfix but it really should be cantfix-without-a-herculean-effort.

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