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

Sergey Shelukhin commented on HBASE-7055:
-----------------------------------------

My take on this is that there appears to be at least few scenarios that sound 
viable. E.g. old data is not as important and read rarely, so we don't care if 
it stays uncompacted and assume blooms will help us ignore these files for the 
keys that are actually being read; or new data is in cache so again there's no 
reason to compact the latest files. Or both.
However, testing if these actually work require setting up a complicated test 
scenario with specific read patterns, over large amounts of data, or a very 
good simulation tool that would estimate read impact (cache usage, how many 
files touched, what is going on in parallel); the will for either of these is 
presently lacking. 
On the other hand, patch is extremely low impact and will be off by default.
So yeah maybe we can keep it for 0.96.X.
                
> port HBASE-6371 tier-based compaction from 0.89-fb to trunk (with changes)
> --------------------------------------------------------------------------
>
>                 Key: HBASE-7055
>                 URL: https://issues.apache.org/jira/browse/HBASE-7055
>             Project: HBase
>          Issue Type: Task
>          Components: Compaction
>    Affects Versions: 0.95.2
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>             Fix For: 0.95.1
>
>         Attachments: HBASE-6371-squashed.patch, HBASE-6371-v2-squashed.patch, 
> HBASE-6371-v3-refactor-only-squashed.patch, 
> HBASE-6371-v4-refactor-only-squashed.patch, 
> HBASE-6371-v5-refactor-only-squashed.patch, HBASE-7055-v0.patch, 
> HBASE-7055-v1.patch, HBASE-7055-v2.patch, HBASE-7055-v3.patch, 
> HBASE-7055-v4.patch, HBASE-7055-v5.patch, HBASE-7055-v6.patch, 
> HBASE-7055-v7.patch, HBASE-7055-v7.patch
>
>
> See HBASE-6371 for details.

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