Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1327510[details]
Dynflow-executor memory usage
Description of problem:
So, I was running some tasks with publishing of content views. And it seems like, dynflow-executor doesn't releases the memory even after the tasks has finished processing.
The memory comes down only after a katello-service restart is performed
The task I ran involved the following steps:
1). Enabled and synchronized 7 repositories in Satellite
2). Created 10 Content Views
3). Added all the 7 repositories to each of the content view
4). Published the content views
Actual results:
The memory usage for Dynflow executor shot up to 2 GB from ~450 MB and even after the execution was complete, dynflow-executor memory doesn't seems to come down.
Expected results:
Shouldn't the dynflow executor memory come down after the task execution is complete?
Additional info:
Attached a screenshot from grafana showing the increase in memory for dynflow-executor which is being held even long after the tasks has finished processing.
Marking as duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1434069
The issue here is the way how ruby does the memory management, that doesn't usualy return to the OS, as it assumes it will be using it later. We're adding a way to recycle the executor to put some upper limit to the memory usage.
*** This bug has been marked as a duplicate of bug 1434069 ***
Created attachment 1327510 [details] Dynflow-executor memory usage Description of problem: So, I was running some tasks with publishing of content views. And it seems like, dynflow-executor doesn't releases the memory even after the tasks has finished processing. The memory comes down only after a katello-service restart is performed The task I ran involved the following steps: 1). Enabled and synchronized 7 repositories in Satellite 2). Created 10 Content Views 3). Added all the 7 repositories to each of the content view 4). Published the content views Actual results: The memory usage for Dynflow executor shot up to 2 GB from ~450 MB and even after the execution was complete, dynflow-executor memory doesn't seems to come down. Expected results: Shouldn't the dynflow executor memory come down after the task execution is complete? Additional info: Attached a screenshot from grafana showing the increase in memory for dynflow-executor which is being held even long after the tasks has finished processing.