Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 25 Oct 2012 05:06:16 +0000 (UTC)
From: "ramkrishna.s.vasudevan (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <427778736.26079.1351141577049.JavaMail.jiratomcat@arcas>
In-Reply-To: <1235357548.46464.1339046544119.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HBASE-6184) HRegionInfo was null or empty in
 Meta
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483901#comment-13483901 ] 

ramkrishna.s.vasudevan commented on HBASE-6184:
-----------------------------------------------

[~aoxiang]
Thanks for your update.  So do you think your patch will address this problem? Your explanation seems to be wrt MVCC right?
                
> 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.3
>
>         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
For more information on JIRA, see: http://www.atlassian.com/software/jira