[
https://issues.apache.org/jira/browse/MAPREDUCE-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859695#action_12859695
]
Hemanth Yamijala commented on MAPREDUCE-1288:
---------------------------------------------
I am trying to revisit if this bug continues to be a blocker, in light of the
decision we have taken to rebase trunk as the next new release.
For the default configuration (DefaultTaskController), even though the files
are localized only once irrespective of the number of users accessing them,
since all the files are localized as the TT user and can be accessed by the TT
user, I suppose this is not a problem. For the LinuxTaskController, it seems
like a problem. However, since we are rebasing from trunk, maybe the feature of
public distributed cache files in MAPREDUCE-744 will cover cases that are
otherwise not covered due to this bug. To explain more, either users want to
share files, or they don't. If they do, they can use the public distributed
cache feature which works fine. If they don't want to share, this bug becomes a
non issue.
Based on this, I am tending to think this is not a blocker. Thoughts ?
> DistributedCache localizes only once per cache URI
> --------------------------------------------------
>
> Key: MAPREDUCE-1288
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1288
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: security, tasktracker
> Affects Versions: 0.21.0
> Reporter: Devaraj Das
> Priority: Blocker
> Fix For: 0.21.0
>
>
> As part of the file localization the distributed cache localizer creates a
> copy of the file in the corresponding user's private directory. The
> localization in DistributedCache assumes the key as the URI of the cachefile
> and if it already exists in the map, the localization is not done again. This
> means that another user cannot access the same distributed cache file. We
> should change the key to include the username so that localization is done
> for every user.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
