[
https://issues.apache.org/jira/browse/TRAFODION-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amanda Moran closed TRAFODION-1249.
-----------------------------------
Resolution: Invalid
Scanner not being used at this time
> LP Bug: 1459476 - scanner HBaseJavaVersion check should execute unset
> JAVA_HOME before the hbase -version command
> -----------------------------------------------------------------------------------------------------------------
>
> Key: TRAFODION-1249
> URL: https://issues.apache.org/jira/browse/TRAFODION-1249
> Project: Apache Trafodion
> Issue Type: Bug
> Components: installer
> Reporter: Vladimir Berman
> Assignee: Amanda Moran
>
> The scanner HBaseJavaVersion check uses the hbase -version command to
> determine the Java version that HBase is using. But this method is flawed
> because the version of Java returned by this command depends on the setting
> of $JAVA_HOME and can be different from the real Java version used by the
> HBase processes. Here is an example from Guy that proves this:
> $: echo $JAVA_HOME
> /usr/java/jdk1.6.0_31
> $: hbase -version
> java version "1.6.0_31"
> Java(TM) SE Runtime Environment (build 1.6.0_31-b04)
> Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01, mixed mode)
> $: export JAVA_HOME=/usr/java/jdk1.7.0_67
> $: hbase -version
> java version "1.7.0_67"
> Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
> Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
> When I changed JAVA_HOME, it returned a different version.
> So, this scanner check should be changed to obtain the HBase Java version
> from the running HBase processes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
