[
https://issues.apache.org/jira/browse/MAPREDUCE-6111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149820#comment-14149820
]
Hadoop QA commented on MAPREDUCE-6111:
--------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12671505/MAPREDUCE-6111.patch
against trunk revision 1147b9a.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common:
org.apache.hadoop.mapreduce.v2.util.TestMRApps
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4918//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4918//console
This message is automatically generated.
> Hadoop users' staging directories should be under a user folder
> ---------------------------------------------------------------
>
> Key: MAPREDUCE-6111
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6111
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.5.0, 2.4.1
> Reporter: Jian Fang
> Attachments: MAPREDUCE-6111.patch
>
>
> Right now, Hadoop puts all users' staging directories under
> /tmp/hadoop-yarn/staging/, for example /tmp/hadoop-yarn/staging/hadoop for
> user hadoop, but the directory /tmp/hadoop-yarn/staging is also used for
> other purpose. For example, /tmp/hadoop-yarn/staging/history/ is used to hold
> finished JHS files. The shared parent /tmp/hadoop-yarn/staging makes it
> difficult to track all users' folders without adding extra logic to exclude
> other known folders.
> As a result, we should move all users' folders to a user sub-folder, i.e.,
> /tmp/hadoop-yarn/staging/user/. In this case, user hadoop's staging folder
> becomes /tmp/hadoop-yarn/staging/user/hadoop/.staging.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
