Re: What will happen in maintenance mode

Thanks Joseph. I saw this from mesos [doc site](http://mesos.apache.org/documentation/latest/maintenance/): "Each machine must have at least a hostname or IP included. The hostname is not case-sensitive." From my test, the statement above is not correct, as if I only specific the hostname

Re: Accepting resources with role as framework

Yes if use version before 0.27 After version 0.27, there no need to specific resource roles, and the `--roles` flag will be deprecated. so frameworks with any role is permitted to use the resource. But if want to define which roles can be used, the recommended practice is to only use ACLs.

Re: Possible authentication bug

Might be related to MESOS-2043 ? Can you paste master and agent logs? On Mon, Jul 18, 2016 at 3:13 PM, Douglas Nelson wrote: > I have SSL enabled for mesos and for the most part everything seems to be > working fine. But

Possible authentication bug

I have SSL enabled for mesos and for the most part everything seems to be working fine. But when I stop a slave node for long enough that it shows up with status LOST then I start up the slave again, registration with the master fails: I0718 15:51:45.646260 16791 master.cpp:5495] Authenticating

Re: Accepting resources with role as framework

Wil, Yes, the framework needs to include the role. Note that if a framework doesn't specify the resource's role, the field will be populated with the default value `*` automatically by the protobuf library when the message is serialized. So, any resource object accepted by your framework will

Accepting resources with role as framework

If a framework receives an offer with resources for a specific role and accepts the offer does the framework need to specify the same role on the resources of the task info? I assume yes based on code in resources.cpp but I wanted to confirm. I can't find this explicitly documented anywhere.

Re: Does a executing task has a expiry time?

The behavior and lifetime of a task is up to the executor (which is, in turn, controlled by the framework; which is decided by the operator). The default command executor does not have any timeouts for running tasks. On Mon, Jul 18, 2016 at 2:59 AM, Bryan Fok wrote: >

Re: What will happen in maintenance mode

My guess is that your agents don't match the machines you specified. Note: The maintenance endpoints in Mesos allow you to specify maintenance against non-existent machines, because the operator may add agents on those machines in future. In Mesos' maintenance primitives, a "machine" is a

Re: How to make use of a custom executor?

Thank you for this, it's very helpful. One question, I've been launching two tasks via my custom executor (which just launches stress at the moment), and according to the webui, the second task is being registered as killed instead of finished. Why does it do this? Here's my executor and

Does a executing task has a expiry time?

Hi all Does a executing task has a expiry time? I don't see it in the configurable, but just in case. BR Bryan

What will happen in maintenance mode

Hi all, I'm puzzled in using maintenance mode. I see this from mesos [doc site](http://mesos.apache.org/documentation/latest/maintenance/): ``` When maintenance is triggered by the operator, all agents on the machine are told to shutdown. These agents are removed from the master, which