It is hard to say with the information provided. I would check the slave log the failure node. I suspect the failure is recorded there.
otherwise more information is necessary: 1. the marathon job (did you launch with a json file? that would be helpful) 2. the slave logs it could also be useful to understand: 1. the version of mesos and marathon 2. what OS is on the nodes ken > On May 11, 2016, at 3:10 AM, suruchi.kum...@accenture.com wrote: > > I have problem scaling the applications through Marathon. > > I have a setup of two slave nodes.The first slave node having CPU=1 and > RAM=2GB and the Second node having CPU=4 and RAM=8GB. > > It is able to scale maximum 5 instances on the first node but when I tried > scaling it further the host gets changed to the second slave node.And the > task fails to start and error in the debug section of the Marathon UI shows > "Abnormal executor termination". > > I would like to know why is it not getting scheduled on the other slave > node??? > > Can you please help me with this issue. > > Thanks > > > This message is for the designated recipient only and may contain privileged, > proprietary, or otherwise confidential information. If you have received it > in error, please notify the sender immediately and delete the original. Any > other use of the e-mail by you is prohibited. Where allowed by local law, > electronic communications with Accenture and its affiliates, including e-mail > and instant messaging (including content), may be scanned by our systems for > the purposes of information security and assessment of internal compliance > with Accenture policy. > ______________________________________________________________________________________ > > www.accenture.com <http://www.accenture.com/>
