fix: pass cas api cpus explicitly to the process #199
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
smrz2001
force-pushed
the
feature/aes-204-pass-cas-api-cpus-explicitly-in-keramik
branch
from
9691ce3
to
5161561
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The code for CAS API clustering (launching as many NodeJS processes as their are CPUs available) is not working in Keramik. This is causing the host's CPUs to be used, which launches 32 processes and causes the container to OOM.
This PR converts the CAS resource limits to an equivalent number of CPUs with a minimum of 1, and passes this number in to the container explicitly.