[
https://issues.apache.org/jira/browse/YARN-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15039519#comment-15039519
]
Sidharta Seethana commented on YARN-3542:
-----------------------------------------
hi [~vvasudev],
Thank you for the patch. I took a look at the patch and it is a bit unclear how
the new configs/resource handler are meant to interact with the existing
{{CgroupsLCEResourcesHandler}} . IMO, one of the goals here is to deprecate
{{CgroupsLCEResourcesHandler}} and use the new resource handler mechanism so
that all the resource handling/isolation is handled in a consistent manner.
Could you please provide a description of the changes introduced in this patch
and what the interaction would be with the existing CPU cgroups implementation
(especially from a configuration perspective) ?
thanks,
-Sidharta
> Re-factor support for CPU as a resource using the new ResourceHandler
> mechanism
> -------------------------------------------------------------------------------
>
> Key: YARN-3542
> URL: https://issues.apache.org/jira/browse/YARN-3542
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Reporter: Sidharta Seethana
> Assignee: Sidharta Seethana
> Priority: Critical
> Attachments: YARN-3542.001.patch, YARN-3542.002.patch
>
>
> In YARN-3443 , a new ResourceHandler mechanism was added which enabled easier
> addition of new resource types in the nodemanager (this was used for network
> as a resource - See YARN-2140 ). We should refactor the existing CPU
> implementation ( LinuxContainerExecutor/CgroupsLCEResourcesHandler ) using
> the new ResourceHandler mechanism.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
