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

Hadoop QA commented on HBASE-14496:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s {color} 
| {color:red} HBASE-14496 does not apply to master. Rebase required? Wrong 
Branch? See https://yetus.apache.org/documentation/latest/precommit-patchnames 
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12767143/HBASE-14496.v2.patch |
| JIRA Issue | HBASE-14496 |
| Powered by | Apache Yetus 0.1.0   http://yetus.apache.org |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/827/console |


This message was automatically generated.



> Compaction improvements: Delayed compaction in RatioBasedCompactionPolicy
> -------------------------------------------------------------------------
>
>                 Key: HBASE-14496
>                 URL: https://issues.apache.org/jira/browse/HBASE-14496
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Vladimir Rodionov
>            Assignee: Vladimir Rodionov
>         Attachments: HBASE-14496.v1.patch, HBASE-14496.v2.patch
>
>
> Delayed compaction feature for RatioBasedCompactionPolicy allows to specify 
> maximum compaction delay for newly created store files. Files will be 
> eligible for compaction only if their age exceeds this delay. This will allow 
> to preserve new data in a block cache. For most applications, the newer the 
> data is the more frequently it is accessed. The frequent compactions of a new 
> store files result in high block cache churn rate and affects read 
> performance and read latencies badly. 
> The configuration will be global, per table, per column family.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to