[HBASE-16244] LocalHBaseCluster start timeout should be configurable

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.1.1
• Fix Version/s: 1.4.0, 0.98.21, 2.0.0

Release Note

When LocalHBaseCluster is started from the command line the Master would give up after 30 seconds due to a hardcoded timeout meant for unit tests. This change allows the timeout to be configured via hbase-site as well as sets it to 5 minutes when LocalHBaseCluster is started from the command line.

• Assignee: Unassigned
• Reporter: Siddharth Wagle
• Created: 19/Jul/16 04:05
• Updated: 18/Jun/18 15:08
• Resolved: 19/Jul/16 21:49

Description

Scenario:

• Ambari metrics service uses HBase in standalone mode
• On restart of AMS HBase, the Master gives up in 30 seconds due to a hardcoded timeout in JVMClusterUtil

2016-07-18 19:24:44,199 ERROR [main] master.HMasterCommandLine: Master exiting
java.lang.RuntimeException: Master not active after 30 seconds
        at org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:194)
        at org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
        at org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:227)
        at org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:139)
        at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
        at org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126)
        at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2526)

• On restart the current Master waits to become active and this leads to the timeout being triggered, waiting for a slightly longer time evades this issue.
• The timeout it seems was meant for unit tests

Attached patch allows the timeout to be configured via hbase-site as well as sets it to 5 minutes for clusters started through HMasterCommandLine.