Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # user >> HRegionInfo was null or empty


Copy link to this message
-
Re: HRegionInfo was null or empty
Perfect, thanks. I will.

JM

2013/1/24, Ted Yu <[EMAIL PROTECTED]>:
> bq. Encountered problems when prefetch META table:
>
> You can ignore the warning.
>
> Cheers
>
> On Thu, Jan 24, 2013 at 1:38 PM, Jean-Marc Spaggiari <
> [EMAIL PROTECTED]> wrote:
>
>> Hi,
>>
>> I'm getting this error (multiple corrurances) while running a MR which
>> is populating an empty table. MR is run against the 'entry' table
>> where I get each line and store the CRC into 'entry_crc' table.
>>
>> 2013-01-24 12:49:01,664 WARN
>>
>> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation:
>> Encountered problems when prefetch META table:
>> java.io.IOException: HRegionInfo was null or empty in Meta for
>> entry_crc, row=entry_crc,\x00\x00\x00\x00\xBF\xB0\xE4>
>> bluejacketsxtra.dispatch.com,99999999999999
>>         at
>> org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:170)
>>         at
>> org.apache.hadoop.hbase.client.MetaScanner.access$000(MetaScanner.java:54)
>>         at
>> org.apache.hadoop.hbase.client.MetaScanner$1.connect(MetaScanner.java:133)
>>         at
>> org.apache.hadoop.hbase.client.MetaScanner$1.connect(MetaScanner.java:130)
>>         at
>> org.apache.hadoop.hbase.client.HConnectionManager.execute(HConnectionManager.java:365)
>>         at
>> org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:130)
>>         at
>> org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:105)
>>         at
>> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:933)
>>         at
>> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:988)
>>         at
>> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:875)
>>         at
>> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.relocateRegion(HConnectionManager.java:846)
>>         at
>> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getRegionLocation(HConnectionManager.java:746)
>>         at
>> org.apache.hadoop.hbase.client.ServerCallable.connect(ServerCallable.java:82)
>>         at
>> org.apache.hadoop.hbase.client.ServerCallable.withRetries(ServerCallable.java:162)
>>         at
>> org.apache.hadoop.hbase.client.HTable.checkAndPut(HTable.java:873)
>>         at
>> org.spaggiari.mapreduce.GenerateCRC$GenerateCRCMapper.map(GenerateCRC.java:122)
>>         at
>> org.spaggiari.mapreduce.GenerateCRC$GenerateCRCMapper.map(GenerateCRC.java:1)
>>         at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:144)
>>         at
>> org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:764)
>>         at org.apache.hadoop.mapred.MapTask.run(MapTask.java:370)
>>         at org.apache.hadoop.mapred.Child$4.run(Child.java:255)
>>         at java.security.AccessController.doPrivileged(Native Method)
>>         at javax.security.auth.Subject.doAs(Subject.java:415)
>>         at
>> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1121)
>>         at org.apache.hadoop.mapred.Child.main(Child.java:249)
>>
>> I'm wondering if this is normal or not. I saw it once, so I cleaned
>> the table and restarted the job, but I'm seeing it again. So it seems
>> it's reproductible. But it's also only a WARN. Not an error...
>>
>> Show I simply ignore this? Or should I dig a bit?
>>
>> JM
>>
>