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

scylla-jmx OOM when running 5k tables backup tasks #88

Open
fgelcer opened this issue Dec 25, 2019 · 6 comments
Open

scylla-jmx OOM when running 5k tables backup tasks #88

fgelcer opened this issue Dec 25, 2019 · 6 comments
Milestone

Comments

@fgelcer
Copy link

fgelcer commented Dec 25, 2019

it also failed to dump when crashing due to "Permission denied" error:

Dec 25 09:48:05 ip-10-0-244-119.eu-west-1.compute.internal scylla-jmx[3305]: Starting the JMX server
Dec 25 09:49:32 ip-10-0-244-119.eu-west-1.compute.internal scylla-jmx[3305]: java.lang.OutOfMemoryError: Java heap space
Dec 25 09:49:32 ip-10-0-244-119.eu-west-1.compute.internal scylla-jmx[3305]: Dumping heap to java_pid3305.hprof ...
Dec 25 09:49:32 ip-10-0-244-119.eu-west-1.compute.internal scylla-jmx[3305]: Unable to create java_pid3305.hprof: Permission denied

logs will be uploaded and posted in next comment.

@slivne
Copy link
Contributor

slivne commented Dec 25, 2019

you need to change scylla-jmx memory .... /usr/lib/scylla/jmx/scylla-jmx change memory to be
-Xmx1024m

@fgelcer
Copy link
Author

fgelcer commented Dec 25, 2019

you need to change scylla-jmx memory .... /usr/lib/scylla/jmx/scylla-jmx change memory to be
-Xmx1024m

yes, this did the trick... jmx is now up and running.

@tzach
Copy link

tzach commented Dec 25, 2019

you need to change scylla-jmx memory .... /usr/lib/scylla/jmx/scylla-jmx change memory to be
-Xmx1024m

@slivne why not making this the default? (at least for anything bigger than t2)

@avikivity
Copy link
Member

Many machines don't have a gigabyte to spare.

Looks like we're consuming 100-200kB per table, that's crazy.

@tzach
Copy link

tzach commented Dec 26, 2019

Many machines don't have a gigabyte to spare.

Sure, this is why it can be a per machine (or percent) parameter.
It does not make sense to let users fail at this time after time.

@DoronArazii DoronArazii added this to the Backlog milestone May 15, 2023
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

5 participants