I tried to launch a CDH hbase cluster on EC2 using this patch, and I had the opposite problem: the master was not running, the region servers were running.
The master seemed to have exited because of this:
2011-07-14 15:48:26,912 WARN org.apache.hadoop.hdfs.DFSClient: Could not get block locations. Source file "/hbase/hbase.version" - Aborting...
2011-07-14 15:48:26,913 FATAL org.apache.hadoop.hbase.master.HMaster: Unhandled exception. Starting shutdown.
org.apache.hadoop.ipc.RemoteException: java.io.IOException: File /hbase/hbase.version could only be replicated to 0 nodes, instead of 1
I had the same problem over at
WHIRR-240, but there the master survived this (possibly due to improved handling in newer HBase, or maybe due to timing differences). Of course, this was the original topic of this issue ("HBase Master shuts down after only one attempt to access DFS"), but hence it's not enough for the namenode to be up, there need to be actual datanodes. Maybe I'll go for the ordered role startup after all.
Also strange was that all hadoop Java processes (datanode, tasktracker) appeared double, as if they were started twice. Will look into this more tomorrow.