[
https://issues.apache.org/jira/browse/HADOOP-13935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15773862#comment-15773862
]
Anu Engineer commented on HADOOP-13935:
---------------------------------------
[~aw] Thanks for the pointers, envvars does solve the issue. I am going to
resolve this JIRA. Happy Holidays.
> A command to print JAVA_VERSION used by Hadoop/HDFS
> ---------------------------------------------------
>
> Key: HADOOP-13935
> URL: https://issues.apache.org/jira/browse/HADOOP-13935
> Project: Hadoop Common
> Issue Type: Improvement
> Components: common
> Affects Versions: 3.0.0-alpha2
> Reporter: Anu Engineer
> Assignee: Yiqun Lin
> Labels: newbie
>
> The java version used by hadoop is controlled by JAVA_HOME variable defined
> in hadoop_env.sh. We log this information when HDFS starts in the log file.
> {noformat}
> STARTUP_MSG: java = 1.8.0_112
> {noformat}
> However, it is quite possible that a user might have many versions of java
> installed on his/her machine. Generally, users tend to check for the java
> version via
> {noformat}
> java -version
> {noformat}
> This just means we are printing out the java version in the current shell
> path.
> This jira proposes adding a new simple command or an extension to existing
> hadoop version command where the current java version used by hadoop is also
> printed out.
> This avoids customer confusion when they are looking at if the java stack is
> properly configured. For example, checking if JCE is installed correctly.
> This is a very minor change that can be done by modifying hdfs.cmd or hdfs
> shell script in the /bin directory. Thanks to [~sujit] for bringing this to
> my attention.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
