You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Elliott Clark (JIRA)" <ji...@apache.org> on 2014/12/29 19:52:13 UTC
[jira] [Resolved] (HBASE-3761) Lots of concurrent table deletes
messes up .META. prefetch
[ https://issues.apache.org/jira/browse/HBASE-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliott Clark resolved HBASE-3761.
----------------------------------
Resolution: Not a Problem
Client's been re-done and meta now gets changed though different hooks.
I don't think this is applicable anymore. Feel free to open a new task if you see something like this again.
> Lots of concurrent table deletes messes up .META. prefetch
> ----------------------------------------------------------
>
> Key: HBASE-3761
> URL: https://issues.apache.org/jira/browse/HBASE-3761
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Priority: Minor
>
> Creating hundreds of tables with hundreds of regions I ran into this issue doing mass table delete:
> {code}
> 11/04/09 10:26:06 WARN client.HConnectionManager$HConnectionImplementation: Encountered problems when prefetch META table:
> org.apache.hadoop.hbase.TableNotFoundException: Cannot find row in .META. for table: bbb_48, row=bbb_48,T�D��iy%��,99999999999999
> at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:136)
> at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:95)
> at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:648)
> at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:702)
> at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:593)
> at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.relocateRegion(HConnectionManager.java:564)
> at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getRegionLocation(HConnectionManager.java:415)
> at org.apache.hadoop.hbase.client.ServerCallable.instantiateServer(ServerCallable.java:57)
> at org.apache.hadoop.hbase.client.ScannerCallable.instantiateServer(ScannerCallable.java:63)
> at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getRegionServerWithRetries(HConnectionManager.java:1011)
> at org.apache.hadoop.hbase.client.HTable$ClientScanner.nextScanner(HTable.java:1077)
> at org.apache.hadoop.hbase.client.HTable$ClientScanner.initialize(HTable.java:1000)
> at org.apache.hadoop.hbase.client.HTable.getScanner(HTable.java:533)
> {code}
> The table was probably removed between start of prefetch scan and next invocation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)