[
https://issues.apache.org/jira/browse/HBASE-12891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393357#comment-14393357
]
Andrew Purtell commented on HBASE-12891:
----------------------------------------
I reverted, sorry about that.
I can get it to hang as below after a clean and rebuild. Not sure why I didn't
see it the first time, maybe unclean tree.
{noformat}
"main" prio=10 tid=0x00007f00dc008000 nid=0x3c55 waiting on condition [0x00007f0
0e2573000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at
org.apache.hadoop.hbase.zookeeper.ZKUtil.blockUntilAvailable(ZKUtil.java:1865)
at
org.apache.hadoop.hbase.zookeeper.MetaRegionTracker.blockUntilAvailable(MetaRegionTracker.java:203)
at
org.apache.hadoop.hbase.client.ZooKeeperRegistry.getMetaRegionLocation(ZooKeeperRegistry.java:58)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:1157)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:1117)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getRegionLocation(HConnectionManager.java:958)
at
org.apache.hadoop.hbase.client.RegionServerCallable.prepare(RegionServerCallable.java:74)
at
org.apache.hadoop.hbase.client.ScannerCallable.prepare(ScannerCallable.java:124)
at
org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:114)
- locked <0x00000007cc44e268> (a
org.apache.hadoop.hbase.client.RpcRetryingCaller)
at
org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:91)
- locked <0x00000007cc44e268> (a
org.apache.hadoop.hbase.client.RpcRetryingCaller)
at
org.apache.hadoop.hbase.client.ClientScanner.nextScanner(ClientScanner.java:284)
at
org.apache.hadoop.hbase.client.ClientScanner.initializeScannerInConstruction(ClientScanner.java:189)
at
org.apache.hadoop.hbase.client.ClientScanner.<init>(ClientScanner.java:184)
at
org.apache.hadoop.hbase.client.ClientScanner.<init>(ClientScanner.java:110)
at org.apache.hadoop.hbase.client.HTable.getScanner(HTable.java:775)
at
org.apache.hadoop.hbase.catalog.MetaReader.fullScan(MetaReader.java:542)
at
org.apache.hadoop.hbase.catalog.MetaReader.tableExists(MetaReader.java:310)
at
org.apache.hadoop.hbase.client.HBaseAdmin.tableExists(HBaseAdmin.java:308)
at
org.apache.hadoop.hbase.client.HBaseAdmin.checkTableExistence(HBaseAdmin.java:1061)
at
org.apache.hadoop.hbase.client.HBaseAdmin.isTableEnabled(HBaseAdmin.java:1072)
at
org.apache.hadoop.hbase.util.TestHBaseFsck.deleteTable(TestHBaseFsck.java:412)
at
org.apache.hadoop.hbase.util.TestHBaseFsck.testOrphanedTableZNode(TestHBaseFsck.java:2252)
{noformat}
Having been burned twice I'm not going to touch this issue further.
> Parallel execution for Hbck checkRegionConsistency
> --------------------------------------------------
>
> Key: HBASE-12891
> URL: https://issues.apache.org/jira/browse/HBASE-12891
> Project: HBase
> Issue Type: Improvement
> Components: hbck
> Affects Versions: 2.0.0, 0.98.10, 1.1.0
> Reporter: churro morales
> Assignee: Dave Latham
> Labels: performance, scalability
> Fix For: 2.0.0, 1.1.0, 0.98.13
>
> Attachments: HBASE-12891-v1.patch, HBASE-12891-v3.patch,
> HBASE-12891-v4-0.98.patch, HBASE-12891-v4-branch-1.patch,
> HBASE-12891-v4.patch, HBASE-12891.98.patch, HBASE-12891.patch,
> HBASE-12891.patch, HBASE-12891.v2-branch-1.patch,
> HBASE-12891.v2-master.patch, hbase-12891-addendum1.patch
>
>
> We have a lot of regions on our cluster ~500k and noticed that hbck took
> quite some time in checkAndFixConsistency(). [~davelatham] patched our
> cluster to do this check in parallel to speed things up. I'll attach the
> patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
