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 "Junping Du (JIRA)" <ji...@apache.org> on 2013/04/01 10:59:17 UTC
[jira] [Commented] (YARN-311) Dynamic node resource configuration
on RM with JMX interface
[ https://issues.apache.org/jira/browse/YARN-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618705#comment-13618705 ]
Junping Du commented on YARN-311:
---------------------------------
Hi Arun, I understand your concern especially in case Hadoop-9160 haven't been figured out (to go or not). How about we go RPC (and NodeCLI) first? After Hadoop-9160 is figured out, then we can follow up later. So here we can only do necessary code change in RM without expose JMX API (while client-RM RPC change in YARN-312, already a demo patch there). Does this sounds like a reasonable plan for you?
> Dynamic node resource configuration on RM with JMX interface
> ------------------------------------------------------------
>
> Key: YARN-311
> URL: https://issues.apache.org/jira/browse/YARN-311
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager, scheduler
> Reporter: Junping Du
> Assignee: Junping Du
> Attachments: YARN-311-v1.patch, YARN-311-v2.patch, YARN-311-v3.patch, YARN-311-v4.patch, YARN-311-v4.patch
>
>
> As the first step, we go for resource change on RM side and expose JMX API. For design details, please refer proposal and discussion in parent JIRA: YARN-291.
--
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