[
https://issues.apache.org/jira/browse/MYRIAD-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980815#comment-14980815
]
DarinJ commented on MYRIAD-162:
-------------------------------
Close but not quite. We want Myriad to be able to use Resources from both the
frameworkUserRole AND the defaultRole (usually *). So we need to be aware of
both, otherwise you're essentially statically partitioning your data center
instead of reserving resources. The idea isn't hard and shouldn't require a
major refactor. I'm prototyping now, will know more soon.
If you wish to recreate simply add a role with some cpu resources to you're
cluster and set frameworkRole to that role. You may need to ensure you're
tasks require enough cpus/mem that they have to use the new role.
> 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)
