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 "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2015/09/07 19:12:46 UTC
[jira] [Updated] (YARN-3092) Create common ResourceUsage class to
track labeled resource usages in Capacity Scheduler
[ https://issues.apache.org/jira/browse/YARN-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli updated YARN-3092:
------------------------------------------
Labels: 2.6.1-candidate (was: )
Fix Version/s: 2.6.1
Pulled this into 2.6.1 as a dependency. Patch applied cleanly.
Ran all ResourceManager tests before pushing this in.
> Create common ResourceUsage class to track labeled resource usages in Capacity Scheduler
> ----------------------------------------------------------------------------------------
>
> Key: YARN-3092
> URL: https://issues.apache.org/jira/browse/YARN-3092
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: api, client, resourcemanager
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Labels: 2.6.1-candidate
> Fix For: 2.7.0, 2.6.1
>
> Attachments: YARN-3092.1.patch, YARN-3092.2.patch
>
>
> Since we have labels on nodes, so we need to track resource usage *by labels*, includes
> - AM resource (to enforce max-am-resource-by-label after YARN-2637)
> - Used resource (includes AM resource usage)
> - Reserved resource
> - Pending resource
> - Headroom
> Benefits to have such a common class are:
> - Reuse lots of code in different places (Queue/App/User), better maintainability and readability.
> - Can make fine-grained locking (e.g. accessing used resource in a queue doesn't need lock a queue)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)