You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2008/12/05 07:14:44 UTC

[jira] Commented: (HBASE-1048) HLog: Found 0 logs to remove out of total 1450; oldest outstanding seqnum is 162297053 fr om region -ROOT-,,0

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

stack commented on HBASE-1048:
------------------------------

If we have to process 1000+ logs because of regionserver restart, cluster won't come back on line for hours.  Also, checking for logs to delete during roll of log blocks all updates.  Spinning through 1000+ blocks updates a long time.

> HLog: Found 0 logs to remove out of total 1450; oldest outstanding seqnum is 162297053 fr om region -ROOT-,,0
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-1048
>                 URL: https://issues.apache.org/jira/browse/HBASE-1048
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>             Fix For: 0.19.0
>
>         Attachments: 1048.patch
>
>
> Above was in tim sell log just before it OOME'd.  1450 log files are going to mess us up.  Need to clear them.  Catalog tables should probably keep up the old optional flush or, if N commit logs, schedule a flush on the region with the oldest sequent number.
> Bringing into 0.19.0.    Gets in the way of our scaling.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.