[
https://issues.apache.org/jira/browse/YARN-7642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16287616#comment-16287616
]
Weiwei Yang commented on YARN-7642:
-----------------------------------
Dig a bit more into the code, it looks like the problem can be resolved by
adding following code in {{ContainerScheduler#onUpdateContainer}} method
{code}
Container nmContainer = context.getContainers().get(containerId);
if (nmContainer != null) {
nmContainer.getContainerTokenIdentifier()
.setExecutionType(currentType);
}
{code}
this ensures the NM context gets properly updated as long as it handles a
container update event.
> 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
>
> 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]
