You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yum, through the urlgrabber Python module, keeps track of which hosts are the quickest to download files from. This is generally useful, but can cause problems in some situations if it gets out of date (e.g. when cached in a Docker image). Unfortunately, while yum clean all cleans up most cached data, it does not remove the urlgrabber download host timing file.
Version-Release number of selected component (if applicable)
find /var/cache/yum -mindepth 1 -delete # clean up the cache
find /var/cache/yum -name timedhosts
yum -q makecache fast
find /var/cache/yum -name timedhosts
yum clean all
find /var/cache/yum -name timedhosts
Actual results
# find /var/cache/yum -mindepth 1 -delete # clean up the cache
# find /var/cache/yum -name timedhosts
# yum -q makecache fast
# find /var/cache/yum -name timedhosts/var/cache/yum/x86_64/7/timedhosts
# yum clean allLoaded plugins: fastestmirror, ovlCleaning repos: base extras updatesCleaning up everythingCleaning up list of fastest mirrors
# find /var/cache/yum -name timedhosts/var/cache/yum/x86_64/7/timedhosts
#
Expected results
# find /var/cache/yum -name timedhosts
#
Additional info
This is not caused by the fastestmirror plugin, which by default uses a file named timedhosts.txt. It is caused by the timedhosts functionality of urlgrabber. This feature is disabled by default but was enabled in the Yum core in 9fdc18d, which has the following commit message:
enable timedhosts
Q: Make it configurable?
This was never followed up on. While it would be nice if it were possible to configure the use of timedhosts or the path to the file it uses, the primary issue is the fact that the timedhosts file is not removed during cleanup. It probably makes the most sense to handle this in the yum clean metadata command, which is implemented in cleanMetadata.
The text was updated successfully, but these errors were encountered:
Thank you for the report. However, please note that this project has been deprecated and is no longer maintained upstream. Please consider migrating to DNF which is the successor of YUM. That said, I’ll close this issue now.
This is a crosspost of RHBZ #1465172.
Description of problem
Yum, through the urlgrabber Python module, keeps track of which hosts are the quickest to download files from. This is generally useful, but can cause problems in some situations if it gets out of date (e.g. when cached in a Docker image). Unfortunately, while
yum clean all
cleans up most cached data, it does not remove the urlgrabber download host timing file.Version-Release number of selected component (if applicable)
yum: 3.4.3-150.el7.centos
python-urlgrabber: 3.10-8.el7
How reproducible
Trivial.
Steps to Reproduce
As root (or with sudo in front of each command):
find /var/cache/yum -mindepth 1 -delete # clean up the cache find /var/cache/yum -name timedhosts yum -q makecache fast find /var/cache/yum -name timedhosts yum clean all find /var/cache/yum -name timedhosts
Actual results
Expected results
# find /var/cache/yum -name timedhosts #
Additional info
This is not caused by the fastestmirror plugin, which by default uses a file named
timedhosts.txt
. It is caused by the timedhosts functionality of urlgrabber. This feature is disabled by default but was enabled in the Yum core in 9fdc18d, which has the following commit message:This was never followed up on. While it would be nice if it were possible to configure the use of timedhosts or the path to the file it uses, the primary issue is the fact that the timedhosts file is not removed during cleanup. It probably makes the most sense to handle this in the
yum clean metadata
command, which is implemented in cleanMetadata.The text was updated successfully, but these errors were encountered: