0001836: Investigate speeding up the query 'yum repolist all'

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001836

ClearOS

app-base - Base System

public

2014-07-09 13:26

2015-04-28 13:43

Reporter

bchambers

Assigned To

bchambers

Priority

normal

Severity

feature

Reproducibility

N/A

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

Target Version

7.1.0 Beta 1

Fixed in Version

7.1.0 Beta 1

Summary

0001836: Investigate speeding up the query 'yum repolist all'

Description

By adding --cacheonly to the command, we can save a huge amount of time....all it's used for (more digging required) is to determine which repos are enabled/disabled so Marketplace can reflect whether an app can be installed.

Hmm...could this call be removed completely and a better user experience created?

Metadata already knows which repo the app is in/requires....as long as it was advertised well (eg. coming from a test repo), do we want to include inline 'enablerepo=clearos-xyz' to the Marketplace installer?

Something to discuss.

Tags

No tags attached.

Attached Files

Relationships

Notes
(0001307) bchambers (administrator) 2014-11-03 10:45	On COS7 Build, many times, yum repolist would bomb out with: [root@themedevel libraries]# yum --cacheonly repolist all -v --setopt=skip_if_unavailable=true Loading "clearcenter-marketplace" plugin Loading "fastestmirror" plugin Config time: 0.018 Yum version: 3.4.3 ClearCenter Marketplace: fetching repositories... One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Disable the repository, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> 4. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true Since we cache result anyways, don't mess with this parameter.

Issue History
Date Modified	Username	Field	Change
2014-07-09 13:26	bchambers	New Issue
2014-07-09 14:32	user2	Status	new => confirmed
2014-08-27 12:03	user2	Product Version	6.6.0 Beta 1 =>
2014-08-27 12:03	user2	Target Version	6.6.0 Beta 2 => 7.0.0 Alpha 2
2014-10-21 15:33	user2	Target Version	7.0.0 Alpha 2 => 7.1.0 Beta 2
2014-11-03 10:43	bchambers	Assigned To	=> bchambers
2014-11-03 10:43	bchambers	Status	confirmed => acknowledged
2014-11-03 10:45	bchambers	Note Added: 0001307
2014-11-03 10:45	bchambers	Target Version	7.1.0 Beta 2 => 7.0.0 Alpha 2
2014-11-03 10:48	bchambers	Target Version	7.0.0 Alpha 2 => 7.1.0 Beta 2
2014-12-31 10:12	bchambers	Status	acknowledged => assigned
2014-12-31 10:12	bchambers	Status	assigned => resolved
2014-12-31 10:12	bchambers	Fixed in Version	=> 7.1.0 Beta 1
2014-12-31 10:12	bchambers	Resolution	open => fixed
2015-01-19 09:03	user2	Target Version	7.1.0 Beta 2 => 7.1.0 Beta 1
2015-04-28 13:43	user2	Status	resolved => closed

ClearOS Bug Tracker