You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myriad.apache.org by "Santosh Marella (JIRA)" <ji...@apache.org> on 2015/10/29 01:02:27 UTC

[jira] [Commented] (MYRIAD-55) Add a API to "destroy" a Myriad/YARN cluster

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

Santosh Marella commented on MYRIAD-55:
---------------------------------------

Fixed with https://github.com/apache/incubator-myriad/pull/21

> Add a API to "destroy" a Myriad/YARN cluster
> --------------------------------------------
>
>                 Key: MYRIAD-55
>                 URL: https://issues.apache.org/jira/browse/MYRIAD-55
>             Project: Myriad
>          Issue Type: Improvement
>            Reporter: Santosh Marella
>            Assignee: Swapnil Daingade
>             Fix For: Myriad 0.1.0
>
>
> This is similar to "destroy" option in Marathon.
> We need a way to distinguish between accidental death of ResourceManager vs an explicit request from admin to shutdown the YARN cluster (both RM and the NMs that were launched by the framework).  In the former case, Mesos needs to wait until a new instance of the framework connects back and the framework's HA should kick in. In the latter case, the framework should tell mesos that it wants to shut down and it should shut down all the tasks (NMs) that it previously launched.



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