[ https://issues.apache.org/jira/browse/HBASE-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113784#comment-13113784 ]
Eugene Koontz commented on HBASE-4472: -------------------------------------- I think Gary's patch is better. It's simpler - with mine, you have the master modifying things outside itself (i.e. a zookeeper node) before aborting. > MiniHBaseCluster.shutdown() doesn't work if no active master > ------------------------------------------------------------ > > Key: HBASE-4472 > URL: https://issues.apache.org/jira/browse/HBASE-4472 > Project: HBase > Issue Type: Bug > Reporter: Gary Helmling > Attachments: HBASE-4472.delete-zk-cluster-node-on-master-abort.patch, > HBASE-4472.patch, jstack.txt > > > Running tests over in HBASE-4014 brought up this issue. If the active master > in a MiniHBaseCluster has aborted, then calling MiniHBaseCluster.shutdown() > will just hang in JVMClusterUtil.shutdown(), waiting to join each of the > region server threads. > Seems like we should explicitly stop each region server instead of just > relying on an active master instance deleting the cluster status znode? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira