[Pulp-list] /var/cache/pulp filling up?

[Matthew Madey]

I think it's failing to remove the files when they are done. Currently
there are 2G of RPM's in the cache directory, most of them are 0bytes. I'm
syncing with the RHEL7 repository, and I'm seeing every package in the
repository in the cache directory, however, once it had filled /var, the
remaining RPM files were 0 bytes. Is there a way to limit to how much
content is able to be staged in the cache directory before being published
to /var/lib/pulp?

# pwd
/var/cache/pulp/
reserved_resource_worker-1 at ln01c4.ourcompany.com/178b371d-d6a4-4ab2-9d39-435041f20d9f/tmp9qE396


# du -sh /var/cache/pulp/
1.9G    /var/cache/pulp/



On Tue, Mar 15, 2016 at 10:46 PM, Randy Barlow <rbarlow at redhat.com> wrote:

> On Tuesday, March 15, 2016 2:40:11 PM EDT Matthew Madey wrote:
> > I've been running Pulp 2.4 for months, recently installed 2.7 on a
> new
> > machine, and I'm noticing different behavior. /var/cache/pulp is
> filling up
> > with what seems to be repository metadata and filling up /var. I
> have other
> > Pulp servers which have been upgraded to 2.7 and don't exhibit this
> same
> > behavior either. I'm curious as to why this is only affecting new
> > installations. I'd really like to avoid creating a separate file system
> for
> > this, since it doesn't seem to be an issue anywhere else.
>
> Hello Matthew!
>
> We started using /var/cache/pulp as a temporary working space for
> the Celery workers instead of /var/lib, so that it would be a local block
> device for systems that store /var/lib/pulp on NFS (a common
> deployment strategy).
>
> When you say it is filling up, do you mean that it's a large amount of
> bytes in that folder during operation, or do you mean that Pulp is
> failing to remove files from that path when it is done with them?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20160316/161e9c9f/attachment.htm>