Bug 460051 - yum lock should be fair in face of concurrent waiters
Summary: yum lock should be fair in face of concurrent waiters
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-25 19:27 UTC by Frank Ch. Eigler
Modified: 2014-01-21 23:06 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-08-25 19:42:21 UTC
Type: ---


Attachments (Terms of Use)

Description Frank Ch. Eigler 2008-08-25 19:27:57 UTC
Description of problem:
When starting several yum jobs in parallel, starvation can occur.

Version-Release number of selected component (if applicable):
3.2.17-2.fc9

How reproducible:
Usually.

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 19:42:21 UTC
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.