-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Configure BK memory sizes automatically from JVM parameters #3572
Conversation
run integration tests |
run integration tests |
1 similar comment
run integration tests |
run integration tests |
rerun integration tests |
We should enable -XX:+UseCGroupMemoryLimitForHeap for the docker images to ensure that if this is running on a large machine in k8s, that it doesn't try to pull a huge amount of memory. |
In fact, I'm going to hazard a guess that this is why integration tests are failing. |
Not quite, but the failure is related to this change. |
The problem is that DbLedgerStorage is failing when the config key is present but empty:
We want the key to be present (and empty) in the config file so that we can easily override in Docker environment. Moving this to 2.3.1 since it will require a small change in BK side |
👍 we should take the Cgroup stuff into account in our images also though |
Sure, but that can be a bit tricky to enable in a general way because:
|
This was already done in #4297 |
Motivation
In BK 4.9, the DbLedgerStorage is already auto-tuning the mem sizes from the available memory in the JVM. Removing the fixed size default.