RE: Marathon GUI -Scaling An Application Issue.

[aishwarya.adyanthaya]

Hi,

When I deploy the docker image for conatiners, it’s able to bring up the 
container on one of the slave. I believe the resource is being utilized and 
therefore the marathon tries to deploy the container on the other machine but 
it gets an error of “Abnormal executor termination” failed.

The marathon shows that it’s in the deploying wait state.

Out of my two slave nodes, the one that has the lowest  resources, the 
containers are getting launched and not the one with the largest resource.

Thank you.

From: Joseph Wu [mailto:jos...@mesosphere.io]
Sent: 10 May 2016 08:39
To: user <user@mesos.apache.org>
Subject: Re: Marathon GUI -Scaling An Application Issue.

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<mailto: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<http://www.accenture.com>

Re: Marathon GUI -Scaling An Application Issue.

[Joseph Wu]

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,  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
>

Marathon GUI -Scaling An Application Issue.

[aishwarya.adyanthaya]

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