> No resources available to allocate! I think this log should be a normal log because of GLOG_V=20
On Wed, Oct 21, 2015 at 10:52 PM, Jojy Varghese <[email protected]> wrote: > Saw this on master log around the time slave was receiving KillTaskMessage: > > hierarchical.hpp:1326] No resources available to allocate! > > -Jojy > > > > On Oct 19, 2015, at 9:05 AM, Łukasz Adamczyk <[email protected]> > wrote: > > > > Hello, > > > > TL;DR; > > > > I have odd problem with Mesos Agent + External Containerizer: I'm able to > > schedule only 14 tasks per agent (sic!), after reaching that limit my > > mesos-agent ignores mesos.internal.RunTaskMessage from mesos-master. > > > > More details: > > > > Web UI with 14/20 tasks with RUNNING status: > > http://foobar.krakow.pl/mesosproblem/mesos-master-ui1.png > > mesos-agent output with GLOG_V=20 (short version): > > http://foobar.krakow.pl/mesosproblem/mesos-slave-tldr.txt > > mesos-agent output with GLOG_V=20 (full version - 0.8MB): > > http://foobar.krakow.pl/mesosproblem/mesos-slave.txt > > mesos-master output with GLOG_V=20 (full version - 1.8MB): > > http://foobar.krakow.pl/mesosproblem/mesos-master.txt > > Web UI after mesos.internal.ShutdownMessage (due to health check > timeout): > > http://foobar.krakow.pl/mesosproblem/mesos-master-ui2.png > > > > Tested on mesos 0.25 and 0.23, with Marathon 0.10 + External > Containerizer > > + Custom Executor (libmesos 0.23). Can you suggest me what is wrong? > Thanks > > in advance! > > > > Regards, > > Łukasz > > > > -- > > Łukasz Adamczyk > > -- Best Regards, Haosdent Huang
