[
https://issues.apache.org/jira/browse/YARN-9033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852669#comment-16852669
]
Hudson commented on YARN-9033:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #16641 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/16641/])
YARN-9033. ResourceHandlerChain#bootstrap is invoked twice during NM (sunilg:
rev 7861a5eb1afd3b8c485b1db83f3bb21a50928e4e)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/scheduler/ContainerScheduler.java
> ResourceHandlerChain#bootstrap is invoked twice during NM start if
> LinuxContainerExecutor enabled
> -------------------------------------------------------------------------------------------------
>
> Key: YARN-9033
> URL: https://issues.apache.org/jira/browse/YARN-9033
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn
> Reporter: Zhankun Tang
> Assignee: Zhankun Tang
> Priority: Major
> Fix For: 3.3.0
>
> Attachments: YARN-9033-trunk.001.patch, YARN-9033-trunk.002.patch,
> YARN-9033-trunk.003.patch
>
>
> The ResourceHandlerChain#bootstrap will always be invoked in NM's
> ContainerScheduler#serviceInit (Involved by YARN-7715)
> So if LCE is enabled, the ResourceHandlerChain#bootstrap will be invoked
> first and then invoked again in ContainerScheduler#serviceInit.
> But actually, the "updateContainer" invocation in YARN-7715 depend on
> containerId's cgroups path creation in "preStart" method which only happens
> when we use "LinuxContainerExecutor". So the bootstrap of
> ResourceHandlerChain shouldn't happen in ContainerScheduler#serviceInit.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
