[ https://issues.apache.org/jira/browse/YARN-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809797#comment-13809797 ]
Junping Du commented on YARN-311: --------------------------------- The log didn't show it is an build failure (it works well locally), so the jenkins failure above is not related with patch but an accident. Rename it to v12b (exactly the same) patch and submit it again. > Dynamic node resource configuration: core scheduler changes > ----------------------------------------------------------- > > 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-v10.patch, YARN-311-v11.patch, > YARN-311-v12b.patch, YARN-311-v12.patch, YARN-311-v1.patch, > YARN-311-v2.patch, YARN-311-v3.patch, YARN-311-v4.patch, YARN-311-v4.patch, > YARN-311-v5.patch, YARN-311-v6.1.patch, YARN-311-v6.2.patch, > YARN-311-v6.patch, YARN-311-v7.patch, YARN-311-v8.patch, YARN-311-v9.patch > > > As the first step, we go for resource change on RM side and expose admin APIs > (admin protocol, CLI, REST and JMX API) later. In this jira, we will only > contain changes in scheduler. > The flow to update node's resource and awareness in resource scheduling is: > 1. Resource update is through admin API to RM and take effect on RMNodeImpl. > 2. When next NM heartbeat for updating status comes, the RMNode's resource > change will be aware and the delta resource is added to schedulerNode's > availableResource before actual scheduling happens. > 3. Scheduler do resource allocation according to new availableResource in > SchedulerNode. > For more design details, please refer proposal and discussions in parent > JIRA: YARN-291. -- This message was sent by Atlassian JIRA (v6.1#6144)