[jira] [Commented] (YARN-5352) Allow container-executor to use private /tmp
[ https://issues.apache.org/jira/browse/YARN-5352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
[jira] [Commented] (YARN-5352) Allow container-executor to use private /tmp
[
https://issues.apache.org/jira/browse/YARN-5352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384856#comment-15384856
]
Hadoop QA commented on YARN-5352:
-
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 13m 8s
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m
28s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 26s
{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 27s
{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
13s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
22s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 22s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green} 0m 22s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 22s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 24s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
10s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 12m 52s {color}
| {color:red} hadoop-yarn-server-nodemanager in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
18s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 36m 27s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.yarn.server.nodemanager.TestDirectoryCollection |
| |
hadoop.yarn.server.nodemanager.containermanager.queuing.TestQueuingContainerManager
|
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:9560f25 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12818857/YARN-5352-v0.patch |
| JIRA Issue | YARN-5352 |
| Optional Tests | asflicense compile cc mvnsite javac unit |
| uname | Linux 4ec1f4873ecf 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed
Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh
|
| git revision | trunk / cda0a28 |
| Default Java | 1.8.0_91 |
| unit |
https://builds.apache.org/job/PreCommit-YARN-Build/12375/artifact/patchprocess/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt
|
| unit test logs |
https://builds.apache.org/job/PreCommit-YARN-Build/12375/artifact/patchprocess/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-YARN-Build/12375/testReport/ |
| modules | C:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
U:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
|
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/12375/console |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
This message was automatically generated.
> 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
[jira] [Commented] (YARN-5352) Allow container-executor to use private /tmp
[ https://issues.apache.org/jira/browse/YARN-5352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384496#comment-15384496 ] Nathan Roberts commented on YARN-5352: -- This patch doesn't address localization. Thinking was that localization doesn't run application code so while it may create files in /tmp (e.g. hsperf*), I wouldn't expect that to be a significant problem. I can look into addressing localization as well if folks think it's important. > 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
