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

Memory Usage in Scheduler #269

Open
JohnOmernik opened this issue Feb 3, 2017 · 1 comment
Open

Memory Usage in Scheduler #269

JohnOmernik opened this issue Feb 3, 2017 · 1 comment
Labels

Comments

@JohnOmernik
Copy link

I am pulling from master and finding that marathon is killing my scheduler due to over memory usage. I was running with 1024mb and it was dying, then I upped to 2048 and it killed it too, I upped to 3GB of ram, but that seems excessive. Any way to force java to run with a lower amount of memory?

Thanks

@steveniemitz
Copy link
Contributor

steveniemitz commented Feb 3, 2017

You'll want to set -Xmx to control the maximum java heap size. That being said, its always possible there's a memory leak somewhere, however I haven't seen an OOM for a long time, running with a 2 GB heap.

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

No branches or pull requests

2 participants