hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1887) MRAsyncDiskService does not properly absolutize volume root paths
Date Wed, 23 Jun 2010 06:54:50 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881583#action_12881583
] 

Todd Lipcon commented on MAPREDUCE-1887:
----------------------------------------

Ravi: this log message only runs once at tasktracker startup, and the number of volumes is
usually <12. Not worth guarding in isDebugEnabled since it's not going to ever be a bottleneck.

> MRAsyncDiskService does not properly absolutize volume root paths
> -----------------------------------------------------------------
>
>                 Key: MAPREDUCE-1887
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1887
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Aaron Kimball
>            Assignee: Aaron Kimball
>         Attachments: MAPREDUCE-1887.2.patch, MAPREDUCE-1887.3.patch, MAPREDUCE-1887.patch
>
>
> In MRAsyncDiskService, volume names are sometimes specified as relative paths, which
are not converted to absolute paths. This can cause errors of the form "cannot delete </full/path/to/foo>
since it is outside of <relative/volume/root>" even though the actual path is inside
the root. 

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


Mime
View raw message