[
https://issues.apache.org/jira/browse/HADOOP-9165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539749#comment-13539749
]
Vinod Kumar Vavilapalli commented on HADOOP-9165:
-------------------------------------------------
Junping, I'd suggest splitting the YARN and MAPREDUCE docs. I am in favor of
YARN-291 instead of TT changes mainly because it flows so much smoothly in YARN
and also how complicated the TT changes could turn out to be. Please close this
as invalid as you already have YARN and MAPREDUCE specific tickets. Tx.
> Dynamic Resource/Slot Configuration on NM/TT
> --------------------------------------------
>
> Key: HADOOP-9165
> URL: https://issues.apache.org/jira/browse/HADOOP-9165
> Project: Hadoop Common
> Issue Type: New Feature
> Reporter: Junping Du
> Attachments: Elastic Resources for Hadoop-draft v0.1.pdf
>
>
> The current Hadoop MRV1/YARN resource management logic assumes per node
> (TT/NM) resource is static during the lifetime of the TT/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.
--
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
