Can you check the following?
- Are offers being sent to Marathon from both agents? This will show up in the master logs, with at least INFO level logging (default). - Do the resources from your second agent actually satisfy your container's constraints? It would help to see your Marathon app definition and the resource string of your agents. You can find the latter printed at the beginning of the agent's logs. i.e. Agent resources: cpus(*):1; mem(*):1024; disk(*):2048 - Are your tasks not being started? Or are they failing on your second node? On Mon, May 9, 2016 at 7:42 PM, <aishwarya.adyanth...@accenture.com> wrote: > Hi, > > > > I have setup 3 mesos-masters and 2 mesos-slave nodes in my environment. > And I’m trying to deploy Docker containers using Marathon UI. I was able to > run the applications and scale it. > > > > Since my first slave has short of resources ,the application (more than 5 > instances) which m scaling should get distributed but it is not getting > distributed or moved to another slave node which has enough resources > available. > > > > I don’t know why is it happening, so could you please help me with this > issue and is Mesos helps the applications to get distributed in terms of > shortage of resources on a particular slave node??? > > > > > > Thank you, > > ------------------------------ > > 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 >
