[
https://issues.apache.org/jira/browse/HBASE-7893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583844#comment-13583844
]
Pranav Sharma commented on HBASE-7893:
--------------------------------------
I saw the following line in the log file: 2013-02-18 23:53:29,652 INFO
org.apache.hadoop.hbase.regionserver.Store: Completed major compaction of 3
file(s) in <blah>, size=61.8m; total size for store is 61.8m
Also, from my cursory look at this piece of code in
Store.java:requestCompaction, it doesn't look like it is honoring the config at
all.
// major compaction iff all StoreFiles are
included
boolean isMajor = (filesToCompact.size() ==
this.storefiles.size());
if (isMajor) {
// since we're enqueuing a major,
update the compaction wait interval
this.forceMajor = false;
this.majorCompactionTime =
getNextMajorCompactTime();
}
// everything went better than expected. create
a compaction request
int pri = getCompactPriority(priority);
ret = new CompactionRequest(region, this,
filesToCompact, isMajor, pri);
> hbase.hregion.majorcompaction not taking effect.
> ------------------------------------------------
>
> Key: HBASE-7893
> URL: https://issues.apache.org/jira/browse/HBASE-7893
> Project: HBase
> Issue Type: Bug
> Components: Compaction
> Affects Versions: 0.92.2
> Environment: Linux <hostname> 2.6.21.7-2.fc8xen-ec2-v1.0 #1 SMP Tue
> Sep 1 10:25:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
> Fedora release 8 (Werewolf)
> Reporter: Pranav Sharma
>
> For disabling auto major compaction, I configured
> hbase.hregion.majorcompaction = 0 in the config file and restarted the
> cluster. In spite of this, major compaction continues to run everyday. Here
> is the config I set:
> <property>
> <name>hbase.hregion.majorcompaction</name>
> <value>0</value>
> </property>
> What other way can I disable auto major compaction? I expected this config to
> work. What am I doing wrong here?
> Please advice. Thanks a lot.
--
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
