[ https://issues.apache.org/jira/browse/YARN-5764 ]
Samrat Deb deleted comment on YARN-5764:
----------------------------------
was (Author: samrat007):
hi [~devaraj] , [~cheersyang] ,
The patch enabled only for LinuxContainerExecutor (which is for secure)
DefaultContainerExecutor is for unsecure which does not have any code change.
Does that mean that numa enable and actually this patch will work on the secure
cluster ?
Even if we configure numa , it wont use the numa awareness if the cluster is
not secure ?
> NUMA awareness support for launching containers
> -----------------------------------------------
>
> Key: YARN-5764
> URL: https://issues.apache.org/jira/browse/YARN-5764
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: nodemanager, yarn
> Reporter: Olasoji
> Assignee: Devaraj Kavali
> Priority: Major
> Fix For: 3.1.0, 3.2.0
>
> Attachments: NUMA Awareness for YARN Containers.pdf, NUMA Performance
> Results.pdf, YARN-5764-v0.patch, YARN-5764-v1.patch, YARN-5764-v10.patch,
> YARN-5764-v11.patch, YARN-5764-v2.patch, YARN-5764-v3.patch,
> YARN-5764-v4.patch, YARN-5764-v5.patch, YARN-5764-v6.patch,
> YARN-5764-v7.patch, YARN-5764-v8.patch, YARN-5764-v9.patch
>
>
> The purpose of this feature is to improve Hadoop performance by minimizing
> costly remote memory accesses on non SMP systems. Yarn containers, on launch,
> will be pinned to a specific NUMA node and all subsequent memory allocations
> will be served by the same node, reducing remote memory accesses. The current
> default behavior is to spread memory across all NUMA nodes.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
