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

Posted to dev@myriad.apache.org by "Javi Roman (JIRA)" <ji...@apache.org> on 2018/04/22 20:52:00 UTC

[jira] [Closed] (MYRIAD-99) Task names for node managers

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

Javi Roman closed MYRIAD-99.
----------------------------
    Resolution: Fixed

Fixed here https://issues.apache.org/jira/browse/MYRIAD-141

> Task names for node managers
> ----------------------------
>
>                 Key: MYRIAD-99
>                 URL: https://issues.apache.org/jira/browse/MYRIAD-99
>             Project: Myriad
>          Issue Type: Bug
>            Reporter: WalterDalton
>
> In anticipation of being able to run multiple yarn clusters on a mesos cluster with yarn, should we include the framework name that launched he node manager in the node manager task name? Right now I believe it's just size-unique identifier, and it could be framework-size-nm-identifier.
> Like if you had one instance of myriad as yarn-prod and another as yarn-dev eh node manager task names could be yarn-prod-nm-large-%uid% and yarn-dev-nm-small-%uid% 
> This could help with administration and management as well as general organization.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)