TestHTablePool failure
----------------------
Key: HBASE-4355
URL: https://issues.apache.org/jira/browse/HBASE-4355
Project: HBase
Issue Type: Bug
Reporter: Ming Ma
Assignee: Ming Ma
This unit test has been failing on my machine with the following error.
testTableWithStringName(org.apache.hadoop.hbase.client.TestHTablePool$TestHTableThreadLocalPool):
Cluster already running at
/hbase-core-trunk/target/test-data/2e41efb9-7b96-4ab3-abec-c58f467b220c/af01017e-ee3c-46fc-b908-078a3a4e8b52/bfd8e9b4-66da-4322-96bd-6db4564d8f41/d9a97e3d-8ffb-4945-a71e-d059e3bc7274/6cdf0b73-b9a0-45f4-856d-53cd02ecebce/34c41612-9311-4199-9902-cf30a9cb7b9d/33e7bfd5-2519-4349-9a44-d05000e00526/dbc60fd9-756d-4263-9ed1-bbff69ec7a80/0e1bde7e-c966-4c3e-a01c-50ded9cb166b/415e8d51-46f2-4d50-879a-870298a9e1f8/fb165bb9-7d6c-4cf8-970a-e281b9818e97
It looks like TestHTablePool uses nested classes TestHTableReusablePool and
TestHTableThreadLocalPool. Both classes could be instantiated by junit
framework in mulitple threads fashion. Both classes call
HBaseTestingUtilility.startMiniCluster. HBaseTestingUtilility.isRunningCluster
throws this exception.
Is the understanding about junit framework correctly? I don't know why others
haven't got such error.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
