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

Allen Wittenauer commented on HADOOP-11764:
-------------------------------------------

bq. 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.

Fine. What about the service code?  There are lots and lots of options here...

But Configuration should probably populate the system properties when it reads 
in configs though....

bq. 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.

You've just described every version of Unix ever. It's called ARG_MAX and it 
becomes a real problem at extremely long lengths.  It's something we need to be 
vigilant about to make sure it doesn't grow to big.  With shell profiles, it's 
going to get even bigger as 3rd parties add more content...

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

Reply via email to