Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <478308765.1228634624184.JavaMail.jira@brutus>
Date: Sat, 6 Dec 2008 23:23:44 -0800 (PST)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Resolved: (HBASE-1048) HLog: Found 0 logs to remove out of
 total 1450; oldest outstanding seqnum is 162297053 fr om region -ROOT-,,0
In-Reply-To: <1956013632.1228437044204.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-1048.
--------------------------

    Resolution: Fixed

> 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.