Scheduler library API change: method to consume Request/Response API calls

Hello everyone, As you all probably know by now, Greg and I are working on enabling operation feedback for frameworks. I implemented a new ReconcileOperations scheduler API call , which will allow frameworks

REMINDER: Mesos 1.6.0 release

Hey Apache Mesos devs! For all tickets which you want to *definitely* make it into Mesos 1.6.0, ensure that 1.6.0 is set as a 'Target Version', and 'Priority' is set to Blocker. Please make this change ASAP so that I can sync with you on progress and be sure that your patches are in 1.6.0. We

Re: Convention for Backward Compatibility for New Operations in Mesos 1.6

> On Apr 16, 2018, at 2:04 PM, Chun-Hung Hsiao wrote: > > Hi all, > > As some might have already known, we are currently working on patches to > implement the new GROW_VOLUME and SHRINK_VOLUME operations [1]. > > One problem surfaces is that, since the new operations are

Re: Convention for Backward Compatibility for New Operations in Mesos 1.6

> Crashing the agent is definitely not a viable option IMO. > > Why can't we use agent capabilities instead of agent version and reject > such operations at master? This is one of the main reasons we introduced > the concept of framework, master, agent capabilities. > > One thing worth mentioning

Re: Proposal: Constrained upgrades from Mesos 1.6

Thanks Ben! I think that we can take care of this issue by either examining the version present in 'MasterInfo', or by introducing a new master capability. So, no need for constrained upgrades after all. Cheers, Greg On Tue, Apr 10, 2018 at 5:48 PM, Benjamin Mahler wrote:

Re: Convention for Backward Compatibility for New Operations in Mesos 1.6

If we do option 1, then there will be no agent crash since the master won't send any unknown operation to an old agent, so option 2 is not a necessity. On Mon, Apr 16, 2018 at 2:12 PM, Silas Snider wrote: > I think we should definitely do option 2 regardless of whether we do

Re: Convention for Backward Compatibility for New Operations in Mesos 1.6

Are you suggesting that for every new operation we'll introduce a new capability? On Mon, Apr 16, 2018 at 2:14 PM, Vinod Kone wrote: > Crashing the agent is definitely not a viable option IMO. > > Why can't we use agent capabilities instead of agent version and reject >

Re: Convention for Backward Compatibility for New Operations in Mesos 1.6

Crashing the agent is definitely not a viable option IMO. Why can't we use agent capabilities instead of agent version and reject such operations at master? This is one of the main reasons we introduced the concept of framework, master, agent capabilities. On Mon, Apr 16, 2018 at 2:04 PM,

Re: Convention for Backward Compatibility for New Operations in Mesos 1.6

I think we should definitely do option 2 regardless of whether we do option 1 as well, since although in this case it will still crash 1.5.0, at least in the future we won't have to have this worry again. On 4/16/18, 2:04 PM, "Chun-Hung Hsiao" wrote: Hi all,

Re: Question on status update retry in agent

We use explicit ack from Scheduler. Here, is a snippet of the logs. Please see logs for Status Update UUID: a918f5ed-a604-415a-ad62-5a34fb6334ef W0416 00:41:25.843505 124530 status_update_manager.cpp:761] Duplicate status update acknowledgment (UUID: 67f548b4-96cb-4b57-8720-2c8a4ba347e8) for

Convention for Backward Compatibility for New Operations in Mesos 1.6

Hi all, As some might have already known, we are currently working on patches to implement the new GROW_VOLUME and SHRINK_VOLUME operations [1]. One problem surfaces is that, since the new operations are not supported in Mesos 1.5, they will lead to an agent crash during the operation