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 2016/05/16 15:49:13 UTC

[jira] [Updated] (YARN-4832) NM side resource value should get updated if change applied in RM side

     [ https://issues.apache.org/jira/browse/YARN-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Junping Du updated YARN-4832:
-----------------------------
    Attachment: YARN-4832-v2.patch

In v2 patch, incorporate Jian's comments above to remove time tracking in RM side.

> 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, YARN-4832-v2.patch, YARN-4832.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)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org