marathon
marathon copied to clipboard
mesosphere
2863267840 bytes 3GB to compile ????
[@ marathon]$ sbt compile OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00000005e0800000, 2863267840, 0) failed; error='Cannot allocate memory' (errno=12)
There is insufficient memory for the Java Runtime Environment to continue.
Native memory allocation (mmap) failed to map 2863267840 bytes for committing reserved memory.
An error report file with more information is saved as:
/home/software/marathon/hs_err_pid16190.log
WTF increased memory, getting this:
[@marathon]$ sbt compile OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x000000068b2a0000, 5726666752, 0) failed; error='Cannot allocate memory' (errno=12)
There is insufficient memory for the Java Runtime Environment to continue.
Native memory allocation (mmap) failed to map 5726666752 bytes for committing reserved memory.
An error report file with more information is saved as:
/home/software/marathon/hs_err_pid1247.log
I am surprised that the .sbtopts were not picked up. Would you be so kind a create a pull request with an update build manual?
I am surprised that the .sbtopts were not picked up. Would you be so kind a create a pull request with an update build manual?
.sbtopts has mem 8GB ???
I don't care to much about this. I compiled yesterday 1.8.222 and I have same symptoms as #7136. When running
sbt -mem 1024 'run --master m01.local:5050 --zk zk://m01.local:2181/marathon --mesos_user root'
I would like some help to get this fixed.
I think we can remove the mem flag for sbt and just let sbt determine it. That was added 4 years ago.
it is still there, first line https://github.com/mesosphere/marathon/blob/master/.sbtopts
@f1-outsourcing, did you try change it to 4096 and try to compile Marathon. If that works you can just create a pull request and we'll accept it. Thanks 🙂