You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Kevin Odell (JIRA)" <ji...@apache.org> on 2012/08/30 20:17:08 UTC
[jira] [Commented] (HBASE-6684) .META. timeout value is incorrect
[ https://issues.apache.org/jira/browse/HBASE-6684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445154#comment-13445154 ]
Kevin Odell commented on HBASE-6684:
------------------------------------
Still working on Unit tests, but they don't seem related to the patch.
> .META. timeout value is incorrect
> ---------------------------------
>
> Key: HBASE-6684
> URL: https://issues.apache.org/jira/browse/HBASE-6684
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.6
> Reporter: Kevin Odell
> Assignee: Kevin Odell
> Attachments: HBASE-6684.patch
>
>
> We are seeing the timeout value of 2147483647ms which is ~24days. That seems a little high for not talking to META.
> {code}
> 2012-08-27 21:57:04,572 INFO org.apache.hadoop.hbase.regionserver.CompactSplitThread: Running rollback/cleanup of failed split of table,PGE:3659323005:READ:\x7F\xFF\xFE\xC
> 6\xC9\x9DS\x7F,1346030679280.94cf5ab361b0e7d92b0b263ffb995852.; Timed out (2147483647ms)
> org.apache.hadoop.hbase.NotAllMetaRegionsOnlineException: Timed out (2147483647ms)
> at org.apache.hadoop.hbase.catalog.CatalogTracker.waitForMeta(CatalogTracker.java:390)
> at org.apache.hadoop.hbase.catalog.CatalogTracker.waitForMetaServerConnectionDefault(CatalogTracker.java:422)
> at org.apache.hadoop.hbase.catalog.MetaEditor.offlineParentInMeta(MetaEditor.java:109)
> at org.apache.hadoop.hbase.regionserver.SplitTransaction.execute(SplitTransaction.java:290)
> at org.apache.hadoop.hbase.regionserver.CompactSplitThread.split(CompactSplitThread.java:156)
> at org.apache.hadoop.hbase.regionserver.CompactSplitThread.run(CompactSplitThread.java:87)
> 2012-08-27 21:57:04,585 FATAL org.apache.hadoop.hbase.regionserver.HRegionServer: ABORTING region server serverName=hdpr002.va.cust.it,60020,1345819108288, load=(requests=102, regions=187, usedHeap=4699, maxHeap=12281): Abort; we got an error after point-of-no-return
> {code}
--
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