You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2017/03/30 21:33:41 UTC

[jira] [Commented] (MESOS-6058) Register slave in deactivate mode

    [ https://issues.apache.org/jira/browse/MESOS-6058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949891#comment-15949891 ] 

Benjamin Mahler commented on MESOS-6058:
----------------------------------------

This sounds like a "reservation template" feature we've talked about, where the master would apply the reservation before letting the agent's resources be allocated.

This might also be covered by the addition of endpoints to deactivate/activate agents MESOS-7317, depending on how that's solved (if identified by machine vs specific agent id).

> Register slave in deactivate mode
> ---------------------------------
>
>                 Key: MESOS-6058
>                 URL: https://issues.apache.org/jira/browse/MESOS-6058
>             Project: Mesos
>          Issue Type: Improvement
>          Components: agent, master
>            Reporter: Klaus Ma
>
> In my cluster, I'd like to reserve some resource for one application, dynamic reservation feature is used because the reservation maybe changed. But when  a slave register to the master, some tasks from other frameworks maybe dispatched to the new slave before reservation. The proposal is to enable slave register in deactivate mode, and activate it after configuration, e.g. dynamic reservation.
> cc [~kaysoky]/[~jvanremoortere]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)