Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Tue, 29 Sep 2015 00:16:04 +0000 (UTC)
From: "Jie Yu (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12901188.1443484755000.97146.1443485764122@Atlassian.JIRA>
In-Reply-To: <JIRA.12901188.1443484755000@Atlassian.JIRA>
References: <JIRA.12901188.1443484755000@Atlassian.JIRA>
 <JIRA.12901188.1443484755677@arcas>
Subject: [jira] [Commented] (MESOS-3547) Investigate self-hosting Mesos
 processes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jie Yu commented on MESOS-3547:
-------------------------------

Flying by... This is really interesting! Wondering if slave itself can be a "persistent task" or not? The cyclic dependency means that we need some sort of bootstrapping. Having a bootstrapping means maybe we can do self slave upgrading? Just some random thoughts :)

> 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
>
> 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)