Varun Vasudev commented on YARN-3542:

All the existing configurations will continue to work as is. The patch adds a 
new configuration -

which if set to true will create the cpu handler as part of the resource 
handler chain. None of the other configurations change. If both 
yarn.nodemanager.resource.cpu.enabled and 
yarn.nodemanager.linux-container-executor.resources-handler.class are set, you 
end up in a situation where both objects end up modifying the same file.

> 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

Reply via email to