-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Large memory spike at the very end of repository sync #3311
Labels
Comments
I've seen this before, it happens only when doing a complete-mirror mode sync, so I presume it's related to creating the publication. |
we're actually not using mirror_mode. here's the completed output of the task, and you can see no publication was created:
let me grab the remote configuration |
Oh, hmm. Interesting. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
"rpm": "3.23.0",
"core": "3.38.0"
Describe the bug
We recently set our memory limits to 4G on our pulp worker pods, and this was not enough to sync RHEL 8 Appstream. The sync would be killed, but all the steps would be complete.
I did a local sync and saw memory spike at the very end of the sync up to 3.7 GB. Here's a link to the memory stats: https://docs.google.com/spreadsheets/d/1AE3_QKFdQIO6MUSUgWFMm_-fDEzUI6IYurp3-4AE-fA/edit#gid=0
Its very likely that it spiked over 4GB, but due to sampling frequency, i only saw 3.7.
To Reproduce
Sync https://cdn.redhat.com/content/dist/rhel8/8/x86_64/appstream/os (with certs that let you access it)
Expected behavior
Not a giant memory spike if possible?
Additional context
Here's the full task output when its killed please excuse the funky formatting) :
The text was updated successfully, but these errors were encountered: