[ https://issues.apache.org/jira/browse/YARN-5352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15435125#comment-15435125 ]
Nathan Roberts commented on YARN-5352: -------------------------------------- bq. I think minimally this needs to be an optional feature (either at the cluster level or at the per-job level) that defaults to false. I agree. I'm thinking that a cluster-level config with default=off, and then the best way to handle container-level support would be via the ongoing work to support docker containers. > Allow container-executor to use private /tmp > --------------------------------------------- > > Key: YARN-5352 > URL: https://issues.apache.org/jira/browse/YARN-5352 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager > Reporter: Nathan Roberts > Assignee: Nathan Roberts > Attachments: YARN-5352-v0.patch > > > It's very common for user code to create things in /tmp. Yes, applications > have means to specify alternate tmp directories but doing so is opt-in and > therefore doesn't happen in many case. At a minimum, linux can use private > namespaces to create a private /tmp for each container so that it's using the > same space allocated to containers and it's automatically cleaned up as part > of container clean-up. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org