[HBASE-2084] [EC2] JAVA_HOME handling broken

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.20.3, 0.90.0
• Hadoop Flags: Reviewed
• Assignee: Andrew Kyle Purtell
• Reporter: Andrew Kyle Purtell
• Created: 31/Dec/09 19:17
• Updated: 12/Oct/12 06:14
• Resolved: 31/Dec/09 20:51

Description

A recent change broke JAVA_HOME handling with respect to how the EC2 images are set up.

Creating/checking security groups
Security group testcluster-master exists, ok
Security group testcluster exists, ok
Security group testcluster-zookeeper exists, ok
Starting ZooKeeper quorum ensemble.
Starting an AMI with ID ami-14927f7d (arch i386) in group testcluster-zookeeper
Waiting for instance i-fb5e7f93 to start: ................. Started ZooKeeper instance i-fb5e7f93 as domU-12-31-39-0C-3C-F3.compute-1.internal
    Public DNS name is ec2-174-129-181-112.compute-1.amazonaws.com.
ZooKeeper quorum is domU-12-31-39-0C-3C-F3.compute-1.internal.
Initializing the ZooKeeper quorum ensemble.
    ec2-174-129-181-112.compute-1.amazonaws.com
+======================================================================+
|      Error: JAVA_HOME is not set and Java could not be found         |
+----------------------------------------------------------------------+
| Please download the latest Sun JDK from the Sun Java web site        |
|       > http://java.sun.com/javase/downloads/ <                      |
|                                                                      |
| HBase requires Java 1.6 or later.                                    |
| NOTE: This script will find Sun Java whether you install using the   |
|       binary or the RPM based installer.                             |
+======================================================================+