You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2016/05/31 16:26:13 UTC
[jira] [Moved] (HADOOP-13225) Allow DataNode to be started with
numactl
[ https://issues.apache.org/jira/browse/HADOOP-13225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer moved HDFS-10370 to HADOOP-13225:
--------------------------------------------------
Assignee: (was: Dave Marion)
Component/s: (was: datanode)
scripts
Issue Type: New Feature (was: Improvement)
Key: HADOOP-13225 (was: HDFS-10370)
Project: Hadoop Common (was: Hadoop HDFS)
> Allow DataNode to be started with numactl
> -----------------------------------------
>
> Key: HADOOP-13225
> URL: https://issues.apache.org/jira/browse/HADOOP-13225
> Project: Hadoop Common
> Issue Type: New Feature
> Components: scripts
> Reporter: Dave Marion
> Attachments: HDFS-10370-1.patch, HDFS-10370-2.patch, HDFS-10370-3.patch, HDFS-10370-branch-2.004.patch, HDFS-10370.004.patch
>
>
> Allow numactl constraints to be applied to the datanode process. The implementation I have in mind involves two environment variables (enable and parameters) in the datanode startup process. Basically, if enabled and numactl exists on the system, then start the java process using it. Provide a default set of parameters, and allow the user to override the default. Wiring this up for the non-jsvc use case seems straightforward. Not sure how this can be supported using jsvc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org