[
https://issues.apache.org/jira/browse/YARN-7642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16290553#comment-16290553
]
Weiwei Yang commented on YARN-7642:
-----------------------------------
Hi [~asuresh]
Thanks for trying this out. You are right, those info was correctly updated.
The issue I previously met on the cluster setup was because I did not
explicitly call {{updateContainerResource}} to notify NM to update. I agree
this is working.
But I think we can get the test case in. In updated v2 patch, it only contains
the test case, which verifies
# Promotion/demotion works with or without auto update enabled (by setting
{{yarn.resourcemanager.auto-update.containers}})
# Container state in RM and NM context both updated correctly after promotion
or demotion.
This increase the test coverage and should be helpful for quality insurance.
Does that make sense to you?
> 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: [email protected]
For additional commands, e-mail: [email protected]
