General compilation of Mesos takes ~2GB per simultaneous job (-j N) being used. In general if you have a host with less than 4GB of ram on it, you probably won't be able to compile Mesos even doing it completely sequentially.
That said, that instance has 15GB of ram, so it shouldn't be an issue unless lots of RAM is being used by various tasks, so it very well might be a bug. On Mon, Oct 6, 2014 at 3:32 PM, Dominic Hamon <[email protected]> wrote: > I don't know if anyone has successfully built mesos in a VM on EC2. > Linking specifically takes a lot of memory. > > I don't have specific numbers though, I'm afraid. > > On Mon, Oct 6, 2014 at 3:30 PM, Valeriu Mutu <[email protected]> wrote: > >> Hello, >> >> I'm new to Mesos and have successfully installed it and begun playing >> with it. >> >> When running 'make check' I ran into an out-of-memory situation and the >> vm was rebooted: >> Oct 6 22:00:08 ip-10-239-168-141 kernel: Task in >> /mesos_test/bc077378-d71b-499f-adea-2d7c933e5db6 killed as a result of >> limit of /mesos_test/bc077378-d71b-499f-adea-2d7c933e5db6 >> [...] >> Oct 6 22:00:08 ip-10-239-168-141 kernel: Memory cgroup out of memory: >> Kill process 3120 (balloon-executo) score 993 or sacrifice child >> Oct 6 22:00:08 ip-10-239-168-141 kernel: Killed process 3120, UID 0, >> (balloon-executo) total-vm:861460kB, anon-rss:97384kB, file-rss:2768kB >> >> What are the minimum hardware requirements for running 'make check'? >> >> I'm using an m3.xlarge ec2 instance. >> >> -- >> Valeriu Mutu >> > > > > -- > Dominic Hamon | @mrdo | Twitter > *There are no bad ideas; only good ideas that go horribly wrong.* >
