hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "lovekesh bansal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7312) [Resource Profiles] getMaximumAllocationPerQueue to account for all resources
Date Tue, 10 Oct 2017 13:07:00 GMT

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

lovekesh bansal commented on YARN-7312:
---------------------------------------

[~sunilg] I checked and found that these unit tests have already been failing in the trunk
as against it seems to be failing because of the patch. Not sure how to go forward. Can you
please guide?

> [Resource Profiles] getMaximumAllocationPerQueue to account for all resources
> -----------------------------------------------------------------------------
>
>                 Key: YARN-7312
>                 URL: https://issues.apache.org/jira/browse/YARN-7312
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>    Affects Versions: 3.1.0
>            Reporter: lovekesh bansal
>            Assignee: lovekesh bansal
>             Fix For: 3.1.0
>
>         Attachments: YARN-7312_trunk.001.patch
>
>
> getMaximumAllocationPerQueue has memory and vcores hardcoded. So it should be made generic
for all resources.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message