Re: Re: Cluster history wiped after master leader reelection

2016-03-15 Thread Geoffroy Jabouley
log/> | Marketplace Lending Meetup <http://www.meetup.com/Peer-to-Peer-Lending-P2P/> > On Mar 10 2016, at 11:47 am, Geoffroy Jabouley < > geoffroy.jabou...@gmail.com> wrote: > Hello > > a leader re-election just occured on our cluster (0.25.0). > > It goes fine except t

Cluster history wiped after master leader reelection

2016-03-10 Thread Geoffroy Jabouley
Hello a leader re-election just occured on our cluster (0.25.0). It goes fine except the entire cluster history has been lost. All tasks counters have been resetted to 0, Completed tasks and Terminated frameworks lists are empty. Has anybody experienced this? Regards PS: this is not a blocki

Re: Re: Mesos 0.25 not incresing Staged/Started counters in the UI

2016-02-24 Thread Geoffroy Jabouley
raightforward way of telling how many tasks had been running on the cluster since it is up. Or am i missing something? If you have some tasks which state is not equal to TASK_STAGING, it would become non-zero. On Wed, Feb 24, 2016 at 8:23 PM, Geoffroy Jabouley wrote: > Hi again > > just

Re: Mesos 0.25 not incresing Staged/Started counters in the UI

2016-02-24 Thread Geoffroy Jabouley
Hi again just checked the /metrics/snapshot endpoint. Staged value is zero. Is this normal? { "allocator\/event_queue_dispatches":0.0, "frameworks\/jenkins\/messages_processed":9.0, "frameworks\/jenkins\/messages_received":9.0, "master\/cpus_percent":0.0958, "master\/cp

Mesos 0.25 not incresing Staged/Started counters in the UI

2016-02-23 Thread Geoffroy Jabouley
Hello since we moved to Mesos 0.25, we noticed that in the left column of the UI, in the TASKS part, counters for Staged and Started tasks are always equals to 0. [image: Images intégrées 1] Is this normal? Or maybe a known-issue? With 0.22.1, Started counter was always zero but at least Stage

Re: Weird behavior when stopping the mesos master leader of a HA mesos cluster

2015-03-17 Thread Geoffroy Jabouley
sue, so feel free to post it there as well. > > On Thu, Mar 12, 2015 at 1:34 AM, Geoffroy Jabouley < > geoffroy.jabou...@gmail.com> wrote: > >> Thanks Alex for your answer. I will have a look. >> >> Would it be better to (cross-)post this discussion on the marath

Re: Weird behavior when stopping the mesos master leader of a HA mesos cluster

2015-03-12 Thread Geoffroy Jabouley
ne and a new one (that technically belongs to a new > framework) is started. You can see that frameworks have two different IDs > (check lines 11:31:40.055496 and 11:31:40.785038) in your example. > > Hope that helps, > Alex > > On Tue, Mar 10, 2015 at 4:04 AM, Geoffroy Jabouley

Re: CPU resource allocation: ignore?

2015-03-11 Thread Geoffroy Jabouley
cheduler will try to >> balance their execution. >> >> Cpu and memory are considered required resources for executors and I >> believe the master enforces this. >> >> What are behavior are you trying to achieve? If your jobs don't require >> much cpu t

Re: CPU resource allocation: ignore?

2015-03-11 Thread Geoffroy Jabouley
Hello As cpu relatives shares are *not very* relevant in our heterogenous cluster, we would like to get rid of CPU resources management and only use MEM resources for our cluster and tasks allocation. Even when modifying the isolation flag of our slave to "--isolation=cgroups/mem", we see these i

Re: Weird behavior when stopping the mesos master leader of a HA mesos cluster

2015-03-10 Thread Geoffroy Jabouley
de. In addition to the master logs Alex requested, can > you also provide relevant portions of the slave logs for these tasks? If > the slave processes themselves never failed over, checkpointing and slave > recovery should be irrelevant. Are you running the mesos-slave itself > i

Weird behavior when stopping the mesos master leader of a HA mesos cluster

2015-03-06 Thread Geoffroy Jabouley
Hello we are facing some unexpecting issues when testing high availability behaviors of our mesos cluster. *Our use case:* *State*: the mesos cluster is up (3 machines), 1 docker task is running on each slave (started from marathon) *Action*: stop the mesos master leader process *Expected*: me

Re: Is mesos spamming me?

2015-02-01 Thread Geoffroy Jabouley
es flag. > > > > Yeah but ... the slave is reporting 1863Mb RAM and 2 CPUS - so how come > that is rejected by jenkins which is asking for the default 0.1 cpu and > 512Mb RAM??? > > > Thanks > > > Bob > > > On Sun, Feb 1, 2015 at 6:05 PM, Hepple, Rober

Re: Is mesos spamming me?

2015-01-30 Thread Geoffroy Jabouley
Hello The message means that the received resource offer from Mesos cluster does not meet your jenkins slave requirements (memory or cpu). This is normal message. you can filter logs from specific classes in Jenkins 1. from the webUI, in the "jenkins_url"/log/levels panel, set the logging

Re: Unable to follow "Sandbox" links from Mesos UI.

2015-01-26 Thread Geoffroy Jabouley
Hello just in case, which internet browser are you using? Do you have installed any extensions (NoScript, Ghostery, ...) that could prevent the display /statis/pailer display? I personnaly use NoScript with Firefox, and i have to turn it off on all @IP of our cluster to correctly access slave in

Re: Task Checkpointing with Mesos, Marathon and Docker containers

2014-12-01 Thread Geoffroy Jabouley
ration 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 < > geoffroy.jabou...@gmail.com> wrote: > >> Hello all >> >> thanks for your answers. >> >> Is there a w

Re: Task Checkpointing with Mesos, Marathon and Docker containers

2014-11-26 Thread Geoffroy Jabouley
report back if this doesn't solve the issue for you. > -- > Connor > > > > On Nov 25, 2014, at 07:43, Geoffroy Jabouley < > geoffroy.jabou...@gmail.com> wrote: > > > > Hello > > > > i am currently trying to activate checkpointing for my M

Task Checkpointing with Mesos, Marathon and Docker containers

2014-11-25 Thread Geoffroy Jabouley
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