What release of Pulp does this affect? Does having more memory solve
this problem?
We use pulp nodes, deprecated in 2.12 :-(... and our parent node has
32GB of memory and we've never ran in to this problem before (we are
running Pulp 2.9.2 currently in production.)
Thanks
On 02/17/2017 10:35 AM, Jiri Tyr wrote:
Thanks for the blog post, Michael. I have just one question: Why the
"rpm repo copy all" doesn't walk through all the available types of
content to prevent the program to consume all memory and fail?
On Fri, Feb 17, 2017 at 4:25 PM, Michael Hrivnak <[email protected]
<mailto:[email protected]>> wrote:
Since this is a relatively common issue, I decided to respond via
blog post:
http://pulpproject.org/2017/02/17/why-does-copy-use-lots-of-memory/
<http://pulpproject.org/2017/02/17/why-does-copy-use-lots-of-memory/>
_______________________________________________
Pulp-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/pulp-list
_______________________________________________
Pulp-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/pulp-list
