Issue #1676
closed
OOM when orphan remove on large puppet repo
Description
I synced down the puppet forge repo and then ran an orphan removal. This resulted in an OOM both times I attempted it.
I only have two repos right now in my Pulp instance, one with puppet forge and one with nine puppet modules.
repro steps:
- create a puppet repo with feed URL of puppet forge
- sync (takes awhile)
- run orphan removal
My vm has 3GB of mem, fwiw.
Updated by rbarlow about 8 years ago
This PR might resolve this issue too, but I am not sure:
https://github.com/pulp/pulp/pull/2425
Please try again with tomorrow's nightly and let us know if it is still a problemo.
Updated by rbarlow about 8 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to rbarlow
- Platform Release set to 2.8.0
Updated by rbarlow about 8 years ago
- Status changed from ASSIGNED to CLOSED - WORKSFORME
I attempted the following:
$ pulp-admin puppet repo create --repo-id=forge --feed=http://forge.puppetlabs.com
$ time pulp-admin puppet repo sync run --repo-id=forge
$ pulp-admin orphan remove --all
The orphan remove operation happened relatively quickly (10-15 seconds) and memory did not climb over 100 MB on my celery worker. I chatted with beav on Freenode a bit, and he suggested that creating orphans would help, so I deleted the repository and then re-ran cleanup:
$ pulp-admin puppet repo delete --repo-id forge
$ pulp-admin orphan remove --all
After talking about it, we decided to close this as working. Chris, if you find a way to reproduce this feel free to re-open. If you can provide memory usage information on the celery process that would be helpful too.
Updated by rbarlow about 8 years ago
I should mention that I tried this on a commit from last Thursday to eliminate the OOM related commit I made from yesterday as being the fix. I did this so that I could find a reliable reproducer before testing whether that commit fixed the issue.
Updated by amacdona@redhat.com about 8 years ago
- Platform Release deleted (
2.8.0)
.