hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Marion (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13225) Allow java to be started with numactl
Date Thu, 29 Jun 2017 21:48:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-13225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069033#comment-16069033

Dave Marion commented on HADOOP-13225:

[~aw] I read over your blog post, looks good to me. Thanks for doing this. It explained to
me some things that I was not aware of in the shell script rewrite in trunk. I agree, given
your example in the blog post, that this can be closed and the user now has the ability to
control this. Thanks!

> 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,
> 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

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message