hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] Created: (HBASE-2990) It's possible for regions to not be major compacted for more than hbase.hregion.majorcompaction
Date Mon, 13 Sep 2010 22:32:35 GMT
It's possible for regions to not be major compacted for more than hbase.hregion.majorcompaction
-----------------------------------------------------------------------------------------------

                 Key: HBASE-2990
                 URL: https://issues.apache.org/jira/browse/HBASE-2990
             Project: HBase
          Issue Type: Bug
            Reporter: Jean-Daniel Cryans
            Priority: Critical
             Fix For: 0.90.0


This is something I've seen here since we upgraded to 0.89 since Gets are now Scans, although
I don't currently have any strong evidence that it wasn't happening in 0.20.

I saw this when we began getting alerts on the frontend that some requests were taking more
than 8 seconds to complete. Even getting a value could take more than 3 minutes in the shell.
The first thing I did was major compacting the table that was slow and the problem went away
immediately. Looking in the logs, it seems the compaction transformed 2 files of (total) 550MB
into 5.2MB. Looking back in the logs for September, it appears that that table was never major
compacted and was slowly growing everyday. Some more grepping around showed that quite a few
regions were never major compacted.

I'm still looking at the code, but the issue seems to be that the minor compactions are always
happening on all store files more than once per day on certain regions, meaning that the oldest
timestamp is always smaller than hbase.hregion.majorcompaction and major compactions are never
triggered.

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


Mime
View raw message