You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Thomas Graves (JIRA)" <ji...@apache.org> on 2014/06/09 21:01:10 UTC

[jira] [Updated] (SPARK-1720) use LD_LIBRARY_PATH instead of -Djava.library.path

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

Thomas Graves updated SPARK-1720:
---------------------------------

    Description: I think it would be better to use LD_LIBRARY_PATH rather then -Djava.library.path.  Once  java.library.path is set, it doesn't search LD_LIBRARY_PATH.  In Hadoop we switched to use LD_LIBRARY_PATH instead of java.library.path.  See https://issues.apache.org/jira/browse/MAPREDUCE-4072.  (was: I think it would be better to use LD_LIBRARY_PATH rather then -Djava.library.path.  Once  java.library.path is set, it doesn't search LD_LIBRARY_PATH.  In Hadoop we switched to use LD_LIBRARY_PATH instead of java.library.path.  See https://issues.apache.org/jira/browse/MAPREDUCE-4072.  I'll split this into separate jira.)

> use LD_LIBRARY_PATH instead of -Djava.library.path
> --------------------------------------------------
>
>                 Key: SPARK-1720
>                 URL: https://issues.apache.org/jira/browse/SPARK-1720
>             Project: Spark
>          Issue Type: Bug
>          Components: Deploy
>    Affects Versions: 1.0.0
>            Reporter: Thomas Graves
>
> I think it would be better to use LD_LIBRARY_PATH rather then -Djava.library.path.  Once  java.library.path is set, it doesn't search LD_LIBRARY_PATH.  In Hadoop we switched to use LD_LIBRARY_PATH instead of java.library.path.  See https://issues.apache.org/jira/browse/MAPREDUCE-4072.



--
This message was sent by Atlassian JIRA
(v6.2#6252)