FYI, the default executor will claim 32MB of RAM, so you'll either need to use a custom executor and specify less RAM, or pretend that your slaves have way more memory than they actually do.
On Mon, Sep 21, 2015 at 11:11 AM, Joris Van Remoortere <[email protected]> wrote: > > I launched tasks with 0.00001 cpus and 0.00001 mems > The executor and task is likely taking more than this amount of memory. > Can you check htop to see if you've run out of memory to create more > stacks to launch new threads? > > On Mon, Sep 21, 2015 at 1:34 AM, Dohyung Park <[email protected]> wrote: > >> I am currently using Mesos + Marathon with 4 slaves for the test. >> >> When I launch a lot of tasks with command ping 8.8.8.8 or while true; do >> sleep 1; done;, >> >> at one point, slaves cannot launch a task any more. The states of tasks >> that are newly launched are 'Failed'. >> >> So I checked out stderr of sandbox, then it shows >> >> "Failed to initialize, pthread_create" >> >> I launched tasks with 0.00001 cpus and 0.00001 mems, so enough resources >> to launch a task remained in slaves. >> >> In a slave, ulimit -a shows >> >> *# ulimit -a* >> >> core file size (blocks, -c) 0 >> data seg size (kbytes, -d) unlimited >> scheduling priority (-e) 0 >> file size (blocks, -f) unlimited >> pending signals (-i) 1545932 >> max locked memory (kbytes, -l) 64 >> max memory size (kbytes, -m) unlimited >> *open files (-n) 65535* >> pipe size (512 bytes, -p) 8 >> POSIX message queues (bytes, -q) 819200 >> real-time priority (-r) 0 >> stack size (kbytes, -s) 8192 >> cpu time (seconds, -t) unlimited >> *max user processes (-u) 1545932* >> virtual memory (kbytes, -v) unlimited >> file locks (-x) unlimited >> >> Is there any limit of the number of tasks that can be launched by Mesos >> on a slave? >> > >
