Bug 460051

Summary:	yum lock should be fair in face of concurrent waiters
Product:	[Fedora] Fedora	Reporter:	Frank Ch. Eigler <fche>
Component:	yum	Assignee:	Seth Vidal <skvidal>
Status:	CLOSED CANTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9	CC:	ffesti, james.antill, katzj, pmatilai, tim.lauridsen
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-08-25 19:42:21 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:

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.