Re: Disk Capacity Detection

Chris, There is a workaround. If you wrap up your storage devices prior to starting Mesos, then you can transparently use multiple disks as a single disk. See [1]. ~Joseph [1] https://www.mail-archive.com/user@mesos.apache.org/msg01726.html On Thu, Jul 23, 2015 at 2:31 PM, Jie Yu wrote: > C

Re: Disk Capacity Detection

Chris, Mesos currently only supports a single disk. In other words, if you have multiple disks, Mesos can only manage one of them. You can choose which disk to use by setting --work_dir to the appropriate directory under the given disk. On Thu, Jul 23, 2015 at 2:28 PM, Christopher Ketchum wrote:

Disk Capacity Detection

Hi, I've recently started using the disk resource, and it seems like mesos slaves only detect disk resources mounted on the root directory. Is there anyway to point mesos to storage mounted elsewhere? Should I just pass what I know to be the cumulative storage to the resources flag? Thanks! Chris

Deprecation/Removal of /master/shutdown endpoint

Hi, just as a short reminder: With 0.23 we deprecated the /master/shutdown in favor of the more consistent /master/teardown endpoint. See MESOS-2697 for details. With Mesos 0.24 we will remove the /master/shutdown endpoint completely. Thanks! Joerg

Re: Custom Executor issue, killTask, task LOST

Thanks for the answer David, I ended up doing exactly that. On 23 July 2015 at 17:13, David Greenberg wrote: > It's the responsibility of each executor to shut itself down when it > decides its no longer needed. The idea here is that an executor can stay > running with zero tasks, so that when t

Re: Custom Executor issue, killTask, task LOST

It's the responsibility of each executor to shut itself down when it decides its no longer needed. The idea here is that an executor can stay running with zero tasks, so that when the scheduler decides to launch a task, the scheduler's already initialized, thus saving startup time. To avoid the pr

Custom Executor issue, killTask, task LOST

Hello, *TL;DR*: What is the proper way to kill executor process(tree) from within executor code? I have an executor written in python that I use with Marathon to launch my tasks. I use it to have a control on task status switch STAGING => RUNNING. I launch a long-running subprocess from the `laun