Re: Mesos replicated log dual writes

an see how overwriting an > entry could be expensive. There's no particular restriction on why we must > overwrite the entire entry, except that we currently use the position number > (i.e. 6506690 in your example) as the key in the leveldb implementation. > >> On Tue, Jun 5, 2018

Mesos replicated log dual writes

Recently investigation of logs of aurora around snapshot creations in replicated log come up with this I0601 21:57:27.322444   144 log.cpp:577] Attempting to append 524304 bytes to the logI0601 21:57:27.322501   144 coordinator.cpp:348] Coordinator attempting to write APPEND action at position

Re: Agent reregistration timeout, no TASK_LOST messages

t;> >>> On Tue, Jul 18, 2017 at 1:14 AM, Vinod Kone <vinodk...@apache.org> wrote: >>> >>> On Mon, Jul 17, 2017 at 2:55 PM, Meghdoot bhattacharya < >>> meghdoo...@yahoo.com.invalid> wrote: >>> >>>> When there is no master fail over and a

Re: Agent reregistration timeout, no TASK_LOST messages

at the failed over master can't send> >>> TASK_LOST for tasks that were running on the agent that didn't >> re-register,> >>> it simply doesn't know about them. The only thing the master can do in >> this> >>> situation is send LostSlaveMessage that will

Re: Agent reregistration timeout, no TASK_LOST messages

This looks like a serious bug unless we are missing something. Hoping for clarifications. Thx > On Jul 14, 2017, at 3:52 PM, Renan DelValle wrote: > > Hi all, > > We're using Mesos 1.1.0 and have observed some unexpected behavior with > regards to Agent

Re: question

Jiamin, here it is 5*15 health check timeout and not the reregister use case. So the question is executor not receiving shutdown message? And also it is getting terminated immediately without any graceful shutdown time? This is mesos 1.1 and in context of custom executor for mesos

Re: [Proposal] Multiple Containers in Single Mesos Task

We shared this a month back through a tweet on supporting docker container pods with a single task (namespace collapse and resourcing sharing with parent mesos task) to satisfy certain needs where in we had to treat mesos, docker and docker-compose first class in our ecosystem. Slides:

Re: Multiple framework DRF tuning

resetting it to 0 for all was a quick/easy fix. Thx   From: Joris Van Remoortere <jo...@mesosphere.io> To: "dev@mesos.apache.org" <dev@mesos.apache.org>; meghdoot bhattacharya <meghdoo...@yahoo.com> Cc: Benjamin Mahler <bmah...@apache.org> Sent: Thursday,

Re: Multiple framework DRF tuning

ev@mesos.apache.org>; meghdoot bhattacharya <meghdoo...@yahoo.com> Sent: Wednesday, June 15, 2016 12:47 AM Subject: Re: Multiple framework DRF tuning Your e-mail seems truncated or mangled in some way (at least for me). Could you please resend it? — *Joris Van Remoortere* Mesosphere O

Multiple framework DRF tuning

I wanted to follow up on 2 issues that we discussed few years back on the below blog described in this section Mesos delayed offers to frameworks http://www.ebaytechblog.com/2014/04/04/delivering-ebays-ci-solution-with-apache-mesos-part-i/ We had sample commits back then for private build.