hbase hbck vc2.out_link
Summary:
-ROOT- is okay.
Number of regions: 1
Deployed on: app-hbase-1,60020,1398226921318
.META. is okay.
Number of regions: 1
Deployed on: app-hbase-4,60020,1398226920856
vc2.out_link is okay.
Number of regions: 9
Deployed on: app-hbase-1,60020,1398226921318
app-hbase-2,60020,1398226921328 app-hbase-4,60020,1398226920856
app-hbase-5,60020,1398226920317
0 inconsistencies detected.
Status: OK
On Tue, May 6, 2014 at 9:40 PM, Ted Yu <[email protected]> wrote:
> Have you run hbck on vc2.out_link ?
>
> Cheers
>
> On May 6, 2014, at 6:33 AM, Li Li <[email protected]> wrote:
>
>> I am using 0.94.11
>>
>> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation
>> Encountered problems when prefetch META table:
>> java.io.IOException: HRegionInfo was null or empty in Meta for
>> vc2.out_link, row=vc2.out_link,,99999999999999
>> at
>> org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:157)
>> at
>> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:1062)
>> at
>> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:1124)
>> at
>> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:1004)
>> at
>> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:961)
>> at org.apache.hadoop.hbase.client.HTable.finishSetup(HTable.java:227)
>> at org.apache.hadoop.hbase.client.HTable.<init>(HTable.java:219)
>> at
>> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getTable(HConnectionManager.java:671)
>> at
>> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getTable(HConnectionManager.java:658)
>> at
>> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getTable(HConnectionManager.java:653)
