Skip to content
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

Not setting allocator memory #112

Open
dizlajk opened this issue Feb 22, 2021 · 1 comment
Open

Not setting allocator memory #112

dizlajk opened this issue Feb 22, 2021 · 1 comment

Comments

@dizlajk
Copy link

dizlajk commented Feb 22, 2021

This is more of a question.. Why are you not setting allocator memory here?

memory_settings: ' {"runner":{"xms":"{{memory.runner}}","xmx":"{{memory.runner}}"},"proxy":{"xms":"{{memory.proxy}}","xmx":"{{memory.proxy}}"},"zookeeper":{"xms":"{{memory.zookeeper}}","xmx":"{{memory.zookeeper}}"},"director":{"xms":"{{memory.director}}","xmx":"{{memory.director}}"},"constructor":{"xms":"{{memory.constructor}}","xmx":"{{memory.constructor}}"},"admin-console":{"xms":"{{memory.adminconsole}}","xmx":"{{memory.adminconsole}}"}}'

You set a variable here:

@abhi2v
Copy link

abhi2v commented Mar 18, 2021

I'm seeing this issue as well. even though I updated my bootstrap/main.yml to add "allocator":{"xms":"4G","xmx":"4G"} in the memory_settings variable, the install script is still creating the docker container with only 1 GB (default). Is there a recommended fix for this that we can implement?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants