Ah thanks. Why does it take 2 minutes to change configuration, are you
doing it manually? Scary :)
On Mon, Dec 1, 2014 at 10:43 AM, Geoffroy Jabouley <
geoffroy.jabou...@gmail.com> wrote:
> Hello
>
> the idea is to be able of tuning the mesos slave configuration
> (attributes, resources offers, g
Hello
the idea is to be able of tuning the mesos slave configuration (attributes,
resources offers, general options, ... upgrades?) without altering the
current tasks running on this mesos slave (a dockerized jenkins instance +
docker jenkins slaves for example).
I am setting up a test cluster wi
> I would like to be able to shutdown a mesos-slave for maintenance without
altering the current tasks.
What are you trying to do? If your maintenance operation does not affect
the tasks, why do you need to stop the slave in the first place?
On Wed, Nov 26, 2014 at 1:36 AM, Geoffroy Jabouley <
ge
Hello all
thanks for your answers.
Is there a way of configuring this 75s timeout for slave reconnection?
I think that my problem is that as the task status is lost:
- marathon framework detects the loss and start another instance
- mesos-slave, when restarting, detects the lost task and restart
Hi Geoffroy,
For the Marathon instances, in all released version of Marathon you must supply
the --checkpoint flag to turn on task checkpointing for the framework. We've
changed the default to true starting with the next release.
There is a bug in Mesos where the FrameworkInfo does not get upd
The mesos considers a slave (and its tasks) lost if the slave is down for 75s.
@vinodkone
> On Nov 25, 2014, at 7:43 AM, Geoffroy Jabouley
> wrote:
>
> Hello
>
> i am currently trying to activate checkpointing for my Mesos cloud.
>
> Starting from an application running in a docker containe
Have you tried a more recent version of Mesos/Marathon? Docker support has
landed as a first class containerizer in the Mesos slave, so there is no
need to use deimos.
Niklas
On 25 November 2014 at 07:43, Geoffroy Jabouley wrote:
> Hello
>
> i am currently trying to activate checkpointing for m
Hello
i am currently trying to activate checkpointing for my Mesos cloud.
Starting from an application running in a docker container on the cluster,
launched from marathon, my use cases are the followings:
*UC1: kill the marathon service, then restart after 2 minutes.*
*Expected*: the mesos task
8 matches
Mail list logo
