hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Weiwei Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7642) Container execution type is not updated after promotion/demotion in NMContext
Date Wed, 13 Dec 2017 11:40:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-7642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16289144#comment-16289144
] 

Weiwei Yang commented on YARN-7642:
-----------------------------------

Attached v1 patch,

* Fixed the bug by updating the context in NM when handling container update events
* Added test cases in {{TestAMRMClient}} to verify NM context gets correctly updated after
promotion
* Added a UT parameter in {{TestAMRMClient}} to cover: 1) auto-update.containers enabled;
2) auto-update.containers disabled;

> Container execution type is not updated after promotion/demotion in NMContext
> -----------------------------------------------------------------------------
>
>                 Key: YARN-7642
>                 URL: https://issues.apache.org/jira/browse/YARN-7642
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 2.9.0
>            Reporter: Weiwei Yang
>            Assignee: Weiwei Yang
>            Priority: Critical
>         Attachments: YARN-7642.001.patch
>
>
> Found this bug while working on YARN-7617. After calling API to promote a container from
OPPORTUNISTIC to GUARANTEED, node manager web page still shows the container execution type
as OPPORTUNISTIC. Looks like the container execution type in NMContext was not updated accordingly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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


Mime
View raw message