You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2015/04/06 20:57:12 UTC

[jira] [Resolved] (MESOS-428) create the concept of a persistent executor

     [ https://issues.apache.org/jira/browse/MESOS-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kone resolved MESOS-428.
------------------------------
    Resolution: Fixed
      Assignee: Jie Yu

Persistent state access is now possible with persistent primitives.

> create the concept of a persistent executor
> -------------------------------------------
>
>                 Key: MESOS-428
>                 URL: https://issues.apache.org/jira/browse/MESOS-428
>             Project: Mesos
>          Issue Type: Story
>          Components: framework, master, slave
>            Reporter: brian wickman
>            Assignee: Jie Yu
>
> The idea would be to allocate (e.g. via the slave command-line or by communicating directly to a specialized allocator) a static ExecutorInfo that would persist forever and never be a candidate for revocation / garbage collection without manual intervention.  Its resources could still be compressed via oversubscription and re-offered but never outright revoked.  Ideally there would be a mechanism to authenticate a framework and allow it to securely lay claim to a preallocated/persistent executor.
> The use-case is for carving out slices of machines for stateful / persistent services, e.g. HDFS, Kestrel, Redis, MySQL.  Rather than managing this via puppet, we'd manage them with Mesos and leverage the Mesos toolchain and observability stack.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)