Issue #8295
Disc Usage during Repository Sync
Description
While performing a repository sync recently I noticed that the WORKING_DIRECTORY was of a much much larger size than I expected.
It is currently assigned 150GB, yet failed to sync 3 repositories (I believe RHEL7 Source, RHEL7 Debug, and possibly RHEL7 Server) due to running out of disk space.
I was of the understanding that the working directory was not intended to hold the entire repository till completion, but only the individual unit's being transferred, on a successful transfer, that would then be ingested and end up as an artefact and stored in the artefact's path.
I believe an additional side affect of this, is that though units have been downloaded cleanly, and I believe could have been converted to an artefact, this has not been done, and a complete re-download is required as evidenced by the fact that on an additional sync the same behaviour occurs.
Maybe this would be the case any way, unless the artefact is converted to content, I'm unsure of those specifics.
Related issues
History
#2
Updated by dalley 6 days ago
- Related to Issue #8296: Pulp worker directories not cleaned up added
#3
Updated by dalley 6 days ago
- Related to Issue #7316: Files are not being deleted from storage when calling the method delete() added
#4
Updated by daviddavis about 24 hours ago
- Triaged changed from No to Yes
Please register to edit this issue