You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Gergo Repas (JIRA)" <ji...@apache.org> on 2017/12/14 17:43:00 UTC
[jira] [Updated] (YARN-7557) It should be possible to specify
resource types in the fair scheduler increment value
[ https://issues.apache.org/jira/browse/YARN-7557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gergo Repas updated YARN-7557:
------------------------------
Attachment: YARN-7557.000.patch
For the high level summary of the configuration changes, pls see the changes in FairScheduler.md. Besides the unit tests I tested this change on a cluster too, I defined "resource1" with the increment of 100k, and submitted a pi job with -Dmapreduce.map.resource.resource1=250k, and saw in the RM log that 300k has been allocated:
INFO org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger: USER=***** OPERATION=AM Allocated Container TARGET=SchedulerApp RESULT=SUCCESS APPID=application_1513271601137_0005 CONTAINERID=container_1513271601137_0005_01_000002 RESOURCE=<memory:200, vCores:1, resource1: 300k>
> It should be possible to specify resource types in the fair scheduler increment value
> -------------------------------------------------------------------------------------
>
> Key: YARN-7557
> URL: https://issues.apache.org/jira/browse/YARN-7557
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: fairscheduler
> Affects Versions: 3.0.0-beta1
> Reporter: Daniel Templeton
> Assignee: Gergo Repas
> Priority: Critical
> Attachments: YARN-7557.000.patch
>
>
--
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