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

Allen Wittenauer commented on YARN-5456:
----------------------------------------

I have a Kerberized Ubuntu/x86 VM that I generally use for testing things.  
Popped trunk+this patch onto it.  Looks like things are working the way they 
are supposed to.

Ran a simple sleep streaming job and ended up with the following dirs in the 
nm-local-dir:
{code}
root@ku:/tmp/hadoop-yarn/nm-local-dir# find . -user aw -type d -ls
  9367    4 drwxr-s---   4 aw       yarn         4096 Aug  2 16:08 
./usercache/aw
  9368    4 drwxr-s---   3 aw       yarn         4096 Aug  2 16:08 
./usercache/aw/appcache
  9370    4 drwxr-s---   7 aw       yarn         4096 Aug  2 16:08 
./usercache/aw/appcache/application_1470179247859_0001
{code}

after job finished, directories disappeared as expected.

> container-executor support for FreeBSD, NetBSD, and others if conf path is 
> absolute
> -----------------------------------------------------------------------------------
>
>                 Key: YARN-5456
>                 URL: https://issues.apache.org/jira/browse/YARN-5456
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>    Affects Versions: 3.0.0-alpha2
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>         Attachments: YARN-5456.00.patch, YARN-5456.01.patch
>
>
> YARN-5121 fixed quite a few portability issues, but it also changed how it 
> determines it's location to be very operating specific for security reasons.  
> We should add support for FreeBSD to unbreak it's ports entry, NetBSD (the 
> sysctl options are just in a different order), and for operating systems that 
> do not have a defined method, an escape hatch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to