[
https://issues.apache.org/jira/browse/YARN-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207323#comment-15207323
]
Junping Du commented on YARN-4832:
----------------------------------
In demo patch:
1. Register NM will receive new resource back if node's resource is already
defined in dynamic-resources.xml
2. NM heartbeat will receive new resource back if node's resource is defined
dynamic. However, after a specified time (default to be NM LOST time) since
last time resource update in CLI, NM will not receive again.
3. RM have a monitor thread to track timeout for response new resource back.
4. Unit Tests to verify the register/heartbeat behavior.
Will sync patch once YARN-998 get in.
> NM side resource value should get updated if change applied in RM side
> ----------------------------------------------------------------------
>
> Key: YARN-4832
> URL: https://issues.apache.org/jira/browse/YARN-4832
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager, resourcemanager
> Reporter: Junping Du
> Assignee: Junping Du
> Priority: Critical
> Attachments: YARN-4832-demo.patch
>
>
> Now, if we execute CLI to update node (single or multiple) resource in RM
> side, NM will not receive any notification. It doesn't affect resource
> scheduling but will make resource usage metrics reported by NM a bit weird.
> We should sync up new resource between RM and NM.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
