You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Deshi Xiao (JIRA)" <ji...@apache.org> on 2016/03/22 05:57:25 UTC

[jira] [Commented] (MESOS-3547) Investigate self-hosting Mesos processes

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

Deshi Xiao commented on MESOS-3547:
-----------------------------------

what? use mesos to install mesos master? could you please input more detail design doc here.

> Investigate self-hosting Mesos processes
> ----------------------------------------
>
>                 Key: MESOS-3547
>                 URL: https://issues.apache.org/jira/browse/MESOS-3547
>             Project: Mesos
>          Issue Type: Improvement
>          Components: master
>            Reporter: Neil Conway
>              Labels: mesosphere
>
> Right now, Mesos master and slave nodes are managed differently: they use different binaries and startup scripts and require different ops procedures. Some of this asymmetric is essential, but perhaps not all of it is. If Mesos supported a concept of "persistent tasks" (see [MESOS-3545]), it might be possible to implement the Mesos master as such a task -- this might help unify the ops procedures between a master and a slave.



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