mesos-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emre Tekelio─člu <emre.tekelio...@gmail.com>
Subject Re: Mesos Marathon weird behavior
Date Mon, 09 Feb 2015 13:02:50 GMT
Hi Dario

Mesos version 0.21.1, Marathon version 0.7.6.
App config;
{
   "id":"/progressed-io",
   "cmd":"sudo docker run fehmicansaglam/progressed.io",
   "args":null,
   "user":null,
   "env":{

   },
   "instances":5,
   "cpus":0.1,
   "mem":128.0,
   "disk":512.0,
   "executor":"",
   "constraints":[

   ],
   "uris":[

   ],
   "storeUrls":[

   ],
   "ports":[

   ],
   "requirePorts":false,
   "backoffSeconds":1,
   "backoffFactor":1.15,
   "container":null,
   "healthChecks":[

   ],
   "dependencies":[

   ],
   "upgradeStrategy":{
      "minimumHealthCapacity":1.0
   }


Thanks,
Emre

2015-02-09 14:52 GMT+02:00 Dario Rexin <dario@mesosphere.io>:

> Hi Emre,
>
> what are the versions of Mesos and Marathon and what does your app
> definition look like?
>
> Cheers,
> Dario
>
> > On 09 Feb 2015, at 13:50, Emre Tekelio─člu <emre.tekelioglu@gmail.com>
> wrote:
> >
> > Hi,
> > I have a single node mesos cluster on Ubuntu 14.04 host machine, with
> one node mesos-master and one node mesos-slave.
> > I try to deploy and run my dockerized services with marathon but i have
> a weird problem.
> >
> > For example If i start a new app with 5 instance, only one task start
> and the status stuck in "deploying". If i restart the mesos-master, then
> the second task start to run.
> >
> > Each restart for mesos-master cause an increment of a task.
> >
> > Any idea?
> >
> > Regards,
> > Emre
>
>

Mime
View raw message