[ https://issues.apache.org/jira/browse/HADOOP-13225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16067655#comment-16067655 ]
Allen Wittenauer commented on HADOOP-13225: ------------------------------------------- I ended up writing up the cgexec example: https://effectivemachines.com/2016/08/10/taking-control-of-daemons-in-apache-hadoop/ I'm thinking this should be closed as won't fix, given that I don't think we want to get into the business of supporting any particular OS's special start tool given that user's can monkey patch whatever support they want in 3.x. > Allow java 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 > Assignee: Dave Marion > Attachments: HDFS-10370.004.patch, HDFS-10370-1.patch, > HDFS-10370-2.patch, HDFS-10370-3.patch, HDFS-10370-branch-2.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.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org