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 2019/02/26 09:09:00 UTC

[jira] [Updated] (MYRIAD-168) Myriad should be able to use ports from the frameworkRole and the defaultRole.

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

Javi Roman updated MYRIAD-168:
------------------------------
    Fix Version/s:     (was: Myriad 0.3.0)
                   Myriad 0.4.0

> Myriad should be able to use ports from the frameworkRole and the defaultRole.
> ------------------------------------------------------------------------------
>
>                 Key: MYRIAD-168
>                 URL: https://issues.apache.org/jira/browse/MYRIAD-168
>             Project: Myriad
>          Issue Type: Improvement
>          Components: Scheduler
>    Affects Versions: Myriad 0.1.0
>            Reporter: DarinJ
>            Assignee: DarinJ
>            Priority: Minor
>             Fix For: Myriad 0.4.0
>
>
> Currently, Myriad ignored ports from roles other than the default role.  However, one could reserve ports on hosts in the resources file for the framework role myriad runs on.  This would prevent port binding collisions for services needing fixed port such as the Job History Server. 



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