hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4456) distributed filecache: mapred.create.symlink=yes not effective
Date Sun, 19 Oct 2008 19:00:46 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640861#action_12640861
] 

Arun C Murthy commented on HADOOP-4456:
---------------------------------------

Christian, can you please confirm that the URI added to the DistributedCache was the form:
hdfs//<namenode>:<port>/source#target?

The DistributedCache uses the 'URI fragment' as the target for the symlink...

> distributed filecache: mapred.create.symlink=yes not effective
> --------------------------------------------------------------
>
>                 Key: HADOOP-4456
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4456
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.17.2
>            Reporter: Christian Kunz
>
> I wanted to run a pipes job with an executable that has to load libhdfs.so.1 dynamically
and I tried to achieve this by using mapred.create.symlink=yes.
> But I did not see any symbolic links created.
> I might do something wrong, but on the other hand, when looking at the code, it seems
that in mapred/TaskRunner.java the workDir is created after the attempts to create symbolic
links.

-- 
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