hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-291) Dynamic resource configuration on NM
Date Tue, 01 Jan 2013 10:34:13 GMT

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

Junping Du commented on YARN-291:

Divide patch into 4 patches (01 - 04) for easily review:
- 01 patch is most Heartbeat and scheduler changes
- 02 patch is JMX implementation on NodeManager for set/get node's resource
- 03 patch is add interface through ClientRMProtocol to set node's resource
- 04 patch is add CLI based on ClientRMProtocol to get/set node's resource.
Please note that 01 can work independent with 02, or 03 and 04 (need to remove heartbeat change).
I will add more unit tests in each sub-patch later.
> Dynamic resource configuration on NM
> ------------------------------------
>                 Key: YARN-291
>                 URL: https://issues.apache.org/jira/browse/YARN-291
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: nodemanager, scheduler
>            Reporter: Junping Du
>            Assignee: Junping Du
>              Labels: features
>         Attachments: YARN-291-AddClientRMProtocolToSetNodeResource-03.patch, YARN-291-all-v1.patch,
YARN-291-core-HeartBeatAndScheduler-01.patch, YARN-291-JMXInterfaceOnNM-02.patch, YARN-291-YARNClientCommandline-04.patch
> The current Hadoop YARN resource management logic assumes per node resource is static
during the lifetime of the NM process. Allowing run-time configuration on per node resource
will give us finer granularity of resource elasticity. This allows Hadoop workloads to coexist
with other workloads on the same hardware efficiently, whether or not the environment is virtualized.
About more background and design details, please refer: HADOOP-9165.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message