Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1738823610.1204726300720.JavaMail.jira@brutus>
Date: Wed, 5 Mar 2008 06:11:40 -0800 (PST)
From: "Hemanth Yamijala (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-2925) [HOD] Create mapred system directory
 using a naming convention that will avoid clashes in multi-user shared
 cluster scenario.
In-Reply-To: <982917235.1204544210456.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-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hemanth Yamijala updated HADOOP-2925:
-------------------------------------

    Status: Patch Available  (was: Open)

Run through Hudson

> [HOD] Create mapred system directory using a naming convention that will avoid clashes in multi-user shared cluster scenario.
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2925
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2925
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/hod
>    Affects Versions: 0.16.0
>            Reporter: Hemanth Yamijala
>            Assignee: Hemanth Yamijala
>             Fix For: 0.16.1
>
>         Attachments: 2925.1.patch, 2925.2.patch, 2925.patch
>
>
> Currently, HOD generates the name of the mapredsystem directory using the name /mapredsystem/hostname-of-jobtracker.
> In HADOOP-2899, we ran into a scenario where this naming convention could lead to problems in case dfs permissions are enabled. While the bug should ideally be addressed in Hadoop M/R, it will be better that HOD does not generate names that can potentially clash across runs. One way to solve the problem is to do what HOD already does for local log and temp directories - name it using username.torque-job-id, which is going to be pretty unique mostly.

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