[
https://issues.apache.org/jira/browse/HADOOP-11764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389517#comment-14389517
]
Zhijie Shen commented on HADOOP-11764:
--------------------------------------
bq. All of the daemons run through the Configuration class (and probably other
classes as well). It could get set then, if it isn't already.
I'm not sure it's a good idea. Configuration is used by a couple of other
projects in Hadoop ecosystem. It's likely to be a more risky change and expose
something unnecessary to other projects.
bq. So not only do we have an extra -D parameter, -Djava.library.path also has
the exact same content which increases the line length even more. This will
almost certainly break some users at some point in time.
I'm not sure if I understand your point here, but "increasing line length"
doesn't sound like something that will almost certainly break some users at
some point in time, unless those some users are very special to be CLI length
sensitive. One step back, JAVA_LIBRARY_PATH is defined by Hadoop to let users
to customize JNI lib path, and it's not something that brings scaring breakage.
My proposal is to relieve users from manually adding leveldb jni lib path into
JAVA_LIBRARY_PATH, which they anyway have to do to make leveldb work in Hadoop.
> 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)
