Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1156947639.1206638848643.JavaMail.jira@brutus>
Date: Thu, 27 Mar 2008 10:27:28 -0700 (PDT)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3103) [HOD] Hadoop.tmp.dir should not be
 set to cluster directory
In-Reply-To: <1446705982.1206596969727.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hadoop QA commented on HADOOP-3103:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12378704/HADOOP-3103.1.for.17
against trunk revision 619744.

    @author +1.  The patch does not contain any @author tags.

    tests included +1.  The patch appears to include 3 new or modified tests.

    javadoc -1.  The javadoc tool appears to have generated 1 warning messages.

    javac +1.  The applied patch does not generate any new javac compiler warnings.

    release audit +1.  The applied patch does not generate any new release audit warnings.

    findbugs +1.  The patch does not introduce any new Findbugs warnings.

    core tests +1.  The patch passed core unit tests.

    contrib tests +1.  The patch passed contrib unit tests.

Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2078/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2078/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2078/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2078/console

This message is automatically generated.

> [HOD] Hadoop.tmp.dir should not be set to cluster directory
> -----------------------------------------------------------
>
>                 Key: HADOOP-3103
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3103
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/hod
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
>            Priority: Blocker
>             Fix For: 0.16.2
>
>         Attachments: HADOOP-3103, HADOOP-3103.1.for.16, HADOOP-3103.1.for.17, HADOOP-3103.for.16, HADOOP-3103.for.17
>
>
> Currently HOD generates  hadoop.tmp.dir pointing to the cluster directory(hod.clusterdir), which users typically create in their home directories. This hadoop.tmp.dir is used on the client side when a jar is run(org/apache/hadoop/util/RunJar.java). The user home directories might be NFS mounted in some environments, which might result in a hit, for example when running a jar.
> So, HOD *should not* generate hadoop.tmp.dir pointing to cluster directory. Instead, it should use hod.temp-dir, which *is* the location that dfs.client.buffer.dir uses to alleviate any such NFS hit problems. Further, though currently hadoop.tmp.dir is not used on hadoop daemons side, it would be good if HOD generates it on daemons side too, and thus preclude any related problems in future.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.