[
https://issues.apache.org/jira/browse/YARN-9033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16851738#comment-16851738
]
Peter Bacsko edited comment on YARN-9033 at 5/30/19 10:56 AM:
--------------------------------------------------------------
Update: it works, I had to fine-tune permissions & container-executor config.
So again +1 non-binding.
I'll rebase the patch and upload v3.
was (Author: pbacsko):
Update: it works, I had to fine-tune permissions & container-executor config.
So again +1 non-binding.
> 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
> Attachments: YARN-9033-trunk.001.patch, YARN-9033-trunk.002.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]
