[
https://issues.apache.org/jira/browse/HADOOP-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575669#action_12575669
]
Hudson commented on HADOOP-2925:
--------------------------------
Integrated in Hadoop-trunk #421 (See
[http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/421/])
> [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.