Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 24740 invoked from network); 27 Mar 2008 14:09:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Mar 2008 14:09:39 -0000 Received: (qmail 73464 invoked by uid 500); 27 Mar 2008 14:09:37 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 73438 invoked by uid 500); 27 Mar 2008 14:09:37 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 73429 invoked by uid 99); 27 Mar 2008 14:09:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Mar 2008 07:09:37 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Mar 2008 14:08:55 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4A15F234C0AE for ; Thu, 27 Mar 2008 07:07:24 -0700 (PDT) Message-ID: <2007956011.1206626844302.JavaMail.jira@brutus> Date: Thu, 27 Mar 2008 07:07:24 -0700 (PDT) From: "Hemanth Yamijala (JIRA)" 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 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582655#action_12582655 ] Hemanth Yamijala commented on HADOOP-3103: ------------------------------------------ +1 for the patch. Validated against both 16 branch and trunk. Verified the hadoop.tmp.dir value is set to the hod.temp-dir and dfs.client.buffer.dir is set to hadoop.tmp.dir/dfs/tmp. Verified also that while running a job, the jar file is expanded in this directory, and it is cleaned up at the end. > [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.