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

Hudson commented on HBASE-5867:
-------------------------------

Integrated in HBase-0.94-security-on-Hadoop-23 #9 (See 
[https://builds.apache.org/job/HBase-0.94-security-on-Hadoop-23/9/])
    HBASE-7040 Port HBASE-5867 Improve Compaction Throttle Default to 0.94 
(Sergey Shelukhin) (Revision 1402215)

     Result = FAILURE
larsh : 
Files : 
* 
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/CompactSplitThread.java
* 
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/Store.java

                
> Improve Compaction Throttle Default
> -----------------------------------
>
>                 Key: HBASE-5867
>                 URL: https://issues.apache.org/jira/browse/HBASE-5867
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Nicolas Spiegelberg
>            Assignee: Nicolas Spiegelberg
>            Priority: Minor
>             Fix For: 0.96.0
>
>         Attachments: ASF.LICENSE.NOT.GRANTED--D2943.1.patch, 
> HBASE-5867-trunk.patch
>
>
> We recently had a production issue where our compactions fell behind because 
> our compaction throttle was improperly tuned and accidentally upgraded all 
> compactions to the large pool.  The default from HBASE-3877 makes 1 bad 
> assumption: the default number of flushed files in a compaction.  Currently 
> the algorithm is:
> throttleSize ~= flushSize * 2
> This assumes that the basic compaction utilizes 3 files and that all 3 files 
> are compressed.  In this case, "hbase.hstore.compaction.min" == 6 && the 
> values were not very compressible.  Both conditions should be taken into 
> consideration.  As a default, it is less damaging for the large thread to be 
> slightly higher than it needs to be versus having everything accidentally 
> promoted.

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

Reply via email to