You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Jun He (JIRA)" <ji...@apache.org> on 2018/08/21 06:08:00 UTC

[jira] [Commented] (BIGTOP-2519) JAVA_HOME not detected correctly for openjdk 8

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

Jun He commented on BIGTOP-2519:
--------------------------------

[~petevg], does this problem still exist? if yes, any chance to have a patch for 1.3.0 release?

> JAVA_HOME not detected correctly for openjdk 8
> ----------------------------------------------
>
>                 Key: BIGTOP-2519
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-2519
>             Project: Bigtop
>          Issue Type: Bug
>          Components: hadoop
>    Affects Versions: 1.1.0
>            Reporter: Pete Vander Giessen
>            Assignee: Pete Vander Giessen
>            Priority: Minor
>             Fix For: 1.3.0
>
>
> I'm running into an issue where the hadoop namenode fails to start hdfs when using openjdk 8. It appears to be because the namenode scripts rely on the bigtop-detect-javahome script in bigtop_utils, which doesn't detect JAVA_HOME correctly for openjdk 8.
> I'd like to modify the script so that it first tries to figure out java home by looking in /etc/alternatives and deriving JAVA_HOME from the symlink to the java executable. This should work on both Redhat and Debian based distros, in a forwards compatible way. The script would fall back to the more manual process for distros that don't use /etc/alternatives.
> Will submit a patch soon ....



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)