-
Notifications
You must be signed in to change notification settings - Fork 11
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
mdapi build in fedora prod openshift takes up lots of memory and never finishes #212
Comments
Not only does the process take up excessive amounts of memory but it also nearly 100% of CPU resources, thus starving other containers and services of the resources that they need for their proper functioning. I started the build from the same |
I tried using
I suspect that I will have to probably push these releases on PyPI and then install them onto the base container image using pip when building the container to install them without any active virtual environment and system-wide. The aforementioned error has been reported twice (here python-poetry/poetry#6459 and here python-poetry/poetry#7200) and attempted to be fixed (here python-poetry/poetry#7766) but to no avail. There are workarounds to create, activate and use a virtual environment from within a container but frankly, I do not find them convincing. |
This is interesting. I tried installing
Seems like installing from PyPI remains to be the last resort - what do you think @abompard ? |
I pushed a new release on GitHub https://github.com/fedora-infra/mdapi/releases/tag/3.1.3 and an associated new release on PyPI https://pypi.org/project/mdapi/3.1.3/, which happens to be the first release of the project on that platform. I also changed the
This one works just fine.
I am not sure if this is objectively the correct way of doing things but as this is working just fine and I do not have any other solutions present in hand at the moment, I am going to push the necessary changes to the |
@davidkirwan reported that the most recent version has successfully generated the container image and MDAPI v3.1.3 is now deployed in the production environment. Closing this now as FIXED. Thanks for reporting this @nirik! |
mdapi build took about 230GB and caused the node it was on to be unstable. ;(
Here's the logs from the last build:
It got to about 5GB in 10min... ;(
The text was updated successfully, but these errors were encountered: