[YARN-311] Dynamic node resource configuration: core scheduler changes

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.3.0
• Component/s: graceful, resourcemanager, scheduler
• Hadoop Flags: Reviewed
• Assignee: Junping Du
• Reporter: Junping Du
• Created: 04/Jan/13 03:53
• Updated: 25/Oct/19 20:26
• Resolved: 06/Nov/13 02:38

Description

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.

Issue Links

• blocks: YARN-312 Add updateNodeResource in ResourceManagerAdministrationProtocol
• is depended upon by: YARN-671 Add an interface on the RM to move NMs into a maintenance state
• is depended upon by: YARN-998 Keep NM resource updated through dynamic resource config for RM/NM restart
• is depended upon by: YARN-914 (Umbrella) Support graceful decommission of nodemanager
• relates to: YARN-1911 NullPointerException in ResourceOption.getOverCommitTimeout()