reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergiy Matusevych (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1665) Better default value for Java binary path
Date Tue, 08 Nov 2016 22:39:58 GMT

    [ https://issues.apache.org/jira/browse/REEF-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649015#comment-15649015
] 

Sergiy Matusevych commented on REEF-1665:
-----------------------------------------

*UPDATE:* A better solution seems to be using
{code:java}
private static final String DEFAULT_JAVA_PATH = "{{JAVA_HOME}}/bin/java";
{code}
and let Hadoop expand it on the remote side, and implement the same expansion in REEF Local
runtime.


> Better default value for Java binary path
> -----------------------------------------
>
>                 Key: REEF-1665
>                 URL: https://issues.apache.org/jira/browse/REEF-1665
>             Project: REEF
>          Issue Type: Bug
>          Components: REEF Client, REEF Driver
>            Reporter: Sergiy Matusevych
>            Assignee: Sergiy Matusevych
>            Priority: Minor
>              Labels: environment, java, path, runtime
>
> {{JavaLaunchCommandBuilder}} sets the default path to the Java executable  in this way:
> {code:java}
> private static final String DEFAULT_JAVA_PATH = System.getenv("JAVA_HOME") + "/bin/"
+ "java";
> {code}
> That is, *by default* REEF client assumes that
>   1) you have {{JAVA_HOME}} environment variable set, and
>   2) your {{JAVA_HOME}} is the same as the one on the remote host.
> A better solution would be to set
> {code:java}
> DEFAULT_JAVA_PATH = "java";
> {code}
> and assume that java binary is in the system's {{PATH}} - both on the client and in the
cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message