Re: Removing the External Containerizer

+1 For remove this eventually, since modularization become a more recommended way. My concern is should we drop this after we finish container modularization? Because there is no way to implement custom containerizer during the interval between removing the external containerizer and supporting co

Removing the External Containerizer

Hello all, The 'external' containerizer has been deprecated since August and we are now considering removing it permanently before the 0.29 release. Are there any objections to this? The following JIRA suggests that Hadoop on Mesos was still using the External containerizer format. https://issues

RE: Altering agent resrouces after startup

Ah ha! Thanks :) I was confused as I can see most tickets without logging in! -- Aaron Carey Production Engineer - Cloud Pipeline Industrial Light & Magic London 020 3751 9150 From: haosdent [haosd...@gmail.com] Sent: 20 April 2016 11:06 To: user Subject: Re: Al

Re: setting roles in mesos 0.28

On Apr 20 2016, at 1:36 am, Jian Qiu wrote: > It is not necessary to configure --role on master. Actually it should work if you configure --default_role='sparkr' on agent and start marathon with --mesos_role=sparkr. Which version of mesos are you using? And could you at

Re: Altering agent resrouces after startup

>however I can't actually access that ticket. Have you login in https://issues.apache.org/jira/browse/MESOS? Can you add comments in it successfully? On Wed, Apr 20, 2016 at 5:30 PM, Klaus Ma wrote: > @Aaron, thanks for your info; I think MESOS-3059 cover your cases. > > On Wed, Apr 20, 2016 at

Re: Altering agent resrouces after startup

@Aaron, thanks for your info; I think MESOS-3059 cover your cases. On Wed, Apr 20, 2016 at 5:24 PM Aaron Carey wrote: > 2 frameworks minimum, sometimes more (depends what we're doing at the > time). Marathon is always running and we have a couple of custom frameworks > too.. > > > -- > > Aaron C

RE: Altering agent resrouces after startup

2 frameworks minimum, sometimes more (depends what we're doing at the time). Marathon is always running and we have a couple of custom frameworks too.. -- Aaron Carey Production Engineer - Cloud Pipeline Industrial Light & Magic London 020 3751 9150 From: Klaus

RE: Altering agent resrouces after startup

Thanks Klaus, After reading Haosdent's response I have a feeling a ticket may already exist: MESOS-3059 which would work for our usecase, however I can't actually access that ticket. I'm happy to create a new one if needed though? Thanks, Aaron -- Aaron Carey Production Engineer - Cloud Pipel

Re: Altering agent resrouces after startup

For the label/attributes, I think this a case we need to pay attention: the allocator did not count in label/attributes when doing allocation, so the resources maybe assigned to different frameworks. @Aaron, how many frameworks are you running? Thanks Klaus On Wed, Apr 20, 2016 at 5:18 PM Aaron C

RE: Altering agent resrouces after startup

Ah thank you! I tried searching Jira but didn't find that ticket. Yes I think you might be right about the attributes, although I don't seem to be able to get to the MESOS-3059 ticket in Jira, do you know if it's on the roadmap? Thanks, Aaron -- Aaron Carey Production Engineer - Cloud Pipelin

Re: Altering agent resrouces after startup

Hi Aaron, Currently, the resources in slave can NOT be updated after started; the QoS can only report revocable resources. But I think this reasonable requirement to detect resource on the fly; would you help to open an JIRA for this? I think there're two sub-requirement of this scenario: 1. The

Re: Altering agent resrouces after startup

There is a ticket [Allow slave reconfiguration on restart]( https://issues.apache.org/jira/browse/MESOS-1739) related to this and not implement yet. But your requirement seems not related to change resources of agent dynamically. It looks more like change labels/attributes dynamically of agent. On

Altering agent resrouces after startup

Hi All, I was wondering if it was possible somehow to alter an agent's resources after it has started? Example: we are dynamically attaching and detaching EBS volumes to EC2 hosts running as agents. (This is part of our docker volume setup using RexRay). When a host has an EBS volume attached

Re: [Proposal] Remove the default value for agent work_dir

+1 Thanks for doing this! On Tue, Apr 19, 2016 at 11:33 PM, Greg Mann wrote: > It sounds like there's agreement that this is a good idea, so we'll > proceed with the patches. Thanks y'all! > > Greg > > On Wed, Apr 13, 2016 at 3:39 PM, Justin Ryan wrote: > >> I’m +1 on removing the default. >> >