HBase RegionServers Won't Start After Cloudbreak install in AWS

[#1]

I have a 10 node cluster spun up by Cloudbreak in AWS and everything is green in Ambari except all RegionServers didn't start. I can manually start them all successfully but his issue won't help automated setups where it is expected to have all services running before executing jobs.

Here's the Event Log from Cloudbreak:

10/10/2015 10:13:23 PM gpawshdp10node - create in progress: Creating infrastructure10/10/2015 10:15:48 PM gpawshdp10node - available: Infrastructure creation took 145 seconds10/10/2015 10:18:48 PM gpawshdp10node - update in progress: Bootstrapping infrastructure cluster10/10/2015 10:19:39 PM gpawshdp10node - update in progress: Setting up infrastructure metadata10/10/2015 10:19:39 PM gpawshdp10node - update in progress: Starting Ambari cluster containers10/10/2015 10:21:14 PM gpawshdp10node - update in progress: Starting Ambari cluster10/10/2015 10:23:30 PM gpawshdp10node - update in progress: Building Ambari cluster; Ambari server ip: 54.153.5.21610/10/2015 10:43:09 PM gpawshdp10node - available: Ambari cluster built; Ambari server ip: 54.153.5.216

[#2]

@[email protected]

Please post last few lines from region server, Ambari server and HBASE master.

[#3 · Accepted solution]

I think it couldn't reach the Zookeeper server. If you increase the "zookeeper.recovery.retry" : "10" it will be fine.