hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-1493) possible double setting of java.library.path introduced by HADOOP-838
Date Thu, 14 Jun 2007 14:33:26 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Enis Soztutar updated HADOOP-1493:
----------------------------------

    Attachment: HADOOP-1493_v1.0.patch

This patch addresses the issue by merging the paths given by "mapred.child.java.opts" and
the TaskTracker's java.library.path



> possible double setting of java.library.path introduced by HADOOP-838
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-1493
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1493
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.14.0
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 0.14.0
>
>         Attachments: HADOOP-1493_v1.0.patch
>
>
> HADOOP-838 introduced setting java.library.path to run the {{TaskTracker$Child}} from
the TaskTracker's library.path, so that the native lib path is passed to the child. However
if we also want to set -Djava.library.path from the configuration by "mapred.child.java.opts",
than the child java process is called with two -Djava.library.path properties, and java seems
to ignore the former, rather than use the two. This situation prevents using -Djava.library.path
in "mapred.child.java.opts". 

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