[
https://issues.apache.org/jira/browse/HADOOP-11764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14515869#comment-14515869
]
Anubhav Dhoot commented on HADOOP-11764:
----------------------------------------
bq. In the past, we used hadoop.tmp.dir for stuff like this.
This use case of a tmpr is different than normal use cases of tmp directory as
it is executing code from there instead of treating as a directory for data.
yes we can do it via *-env.sh or HADOOP_OPTS. The current solution was doing it
via customizing HADOOP_OPTS in a convenient way for the leveldb setting just
like all other examples of "hadoop_add_param HADOOP_OPTS" in
hadoop-functions.sh. Would be good to document in the shell scripting guide
some conventions on when do we - a) document how to modify HADOOP_OPTS, or b)
or add it to *-env or c) create a new option - as essentially they all end up
adding a System property at the end of the day.
> Hadoop should have the option to use directory other than tmp for extracting
> and loading leveldbjni
> ---------------------------------------------------------------------------------------------------
>
> Key: HADOOP-11764
> URL: https://issues.apache.org/jira/browse/HADOOP-11764
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Anubhav Dhoot
> Assignee: Anubhav Dhoot
> Attachments: YARN-3331.001.patch, YARN-3331.002.patch
>
>
> /tmp can be required to be noexec in many environments. This causes a
> problem when nodemanager tries to load the leveldbjni library which can get
> unpacked and executed from /tmp.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
