[
https://issues.apache.org/jira/browse/HBASE-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293487#comment-13293487
]
Anoop Sam John commented on HBASE-6184:
---------------------------------------
{code}
byte[] searchRow =
HRegionInfo.createRegionName(tableName, row, HConstants.NINES,
- false);
+ true);
{code}
This change will affect the look up in the META table?
When searchRow is created with passing newformat=true, it will add the encoded
name also at the end[<tableName>,<row>,<regionid>.<encodedname>.]. But the
searchRow is used to do metaTable.getRowOrBefore(). Any way after the row we
add HConstants.NINES using which we need to get correct row from META table. I
mean adding this encodedname might not be needed for this lookup
In your issue you are getting the result but in that result the HRegionInfo
seems coming as null only? Do this above change really fix your issue? Do u
facing some other issues?
> HRegionInfo was null or empty in Meta
> --------------------------------------
>
> Key: HBASE-6184
> URL: https://issues.apache.org/jira/browse/HBASE-6184
> Project: HBase
> Issue Type: Bug
> Components: client, io
> Affects Versions: 0.94.0
> Reporter: jiafeng.zhang
> Fix For: 0.94.0
>
> Attachments: HBASE-6184.patch
>
>
> insert data
> hadoop-0.23.2 + hbase-0.94.0
> 2012-06-07 13:09:38,573 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 hbase_one_col,
> row=hbase_one_col,09115303780247449149,99999999999999
> at
> org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:160)
> at
> org.apache.hadoop.hbase.client.MetaScanner.access$000(MetaScanner.java:48)
> at
> org.apache.hadoop.hbase.client.MetaScanner$1.connect(MetaScanner.java:126)
> at
> org.apache.hadoop.hbase.client.MetaScanner$1.connect(MetaScanner.java:123)
> at
> org.apache.hadoop.hbase.client.HConnectionManager.execute(HConnectionManager.java:359)
> at
> org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:123)
> at
> org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:99)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:894)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:948)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:836)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchCallback(HConnectionManager.java:1482)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1367)
> at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:945)
> at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:801)
> at org.apache.hadoop.hbase.client.HTable.put(HTable.java:776)
> at
> org.apache.hadoop.hbase.client.HTablePool$PooledHTable.put(HTablePool.java:397)
> at com.dinglicom.hbase.HbaseImport.insertData(HbaseImport.java:177)
> at com.dinglicom.hbase.HbaseImport.run(HbaseImport.java:210)
> at java.lang.Thread.run(Thread.java:662)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
