[
https://issues.apache.org/jira/browse/HBASE-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-938:
------------------------
Attachment: 938-v7.patch
Now you'll see messages like this if we try to do major compaction on a file
that has already been major compacted:
{code}
2008-11-15 00:19:30,441 [regionserver/0:0:0:0:0:0:0:0:60020.compactor] DEBUG
org.apache.hadoop.hbase.regionserver.HStore: Skipping major compaction because
one major compacted file only and elapsedTime 1250119 is < ttl -1
{code}
> major compaction period is not checked periodically
> ---------------------------------------------------
>
> Key: HBASE-938
> URL: https://issues.apache.org/jira/browse/HBASE-938
> Project: Hadoop HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 0.18.0, 0.18.1
> Environment: HBase 0.18 branch (should be RC1) + Hadoop 0.18 branch
> Reporter: Rong-En Fan
> Assignee: stack
> Priority: Critical
> Fix For: 0.19.0
>
> Attachments: 938-v4.patch, 938-v6.patch, 938-v7.patch, 938.patch,
> major.patch
>
>
> The major compaction period, hbase.hregion.majorcompaction, is not checked
> periodically. Currently, we only request major compaction when the region is
> open or split at which point we check whether the major compaction period is
> due.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
