[
https://issues.apache.org/jira/browse/MYRIAD-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981698#comment-14981698
]
DarinJ commented on MYRIAD-162:
-------------------------------
Without a fix Myriad will work if frameworkRole is not present or set to *, but
fail badly if a frameworkRole is present. For a 0.1.0 release, the easiest
nice things to do are 1. add a check if frameworkRole is present and log a
warning and exit or 2. log and then set role to * anyway. After those options
it's simply to fix it. I'm close to a fix (mem/cpu done working ports now) and
would like to have it for 0.1.0, but it can wait for 0.1.1.
> Myriad Not Correctly Dealing with Resources from Multiple Roles
> ---------------------------------------------------------------
>
> Key: MYRIAD-162
> URL: https://issues.apache.org/jira/browse/MYRIAD-162
> Project: Myriad
> Issue Type: Bug
> Components: Scheduler
> Affects Versions: Myriad 0.1.0
> Environment: Any where frameworkRole is not *
> Reporter: DarinJ
> Assignee: DarinJ
> Fix For: Myriad 0.1.0
>
>
> When using Offers that have Resources from multiple roles, one needs to use
> the setRole(String role) method to specify which role the resource belongs
> to. Myriad currently doesn't do this which causes TASK_LOST, with an error
> in the mesos-master log stating in "attempted to use cpus( * ): 1.2; mem( *
> ): 1305.6; ports( * ): [31005-31005,31006-31006,...] greater than offered
> cpu( * ):1, mem( * ): 1400, ports( * ): [ ... ], cpu(roleA): 3, mem(roleA):
> 10000, ports(roleA): [...].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
