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

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

>From the description, the scenario that was used as a basis for this feature 
>is just compressing mid-range (in time) data preferentially, and avoiding hot 
>data and old data. That makes sense in general case; a specific scenario with 
>large improvement that I can think of is for example spiky data uploads, where 
>relatively large amount of data gets put at once, and only recent data is 
>accessed (not from the last spike but just recent as such). Then it doesn't 
>make a lot of sense to compact recent data with old data, and triggering 
>compaction after every spike doesn't make sense either. This is pure 
>speculation though.
Based on that a more flexible tiered scheme was developed which can also be 
applied to other patterns. I am not sure about size tiers applicability.

Would you be ok if we put this as an example scenario in documentation and 
javadoc?

[~liyin] [~akashnil07] can you clarify if there are other scenarios, for which 
this was
                
> port HBASE-6371 tier-based compaction from 0.89-fb to trunk - first slice 
> (not configurable by cf or dynamically)
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-7055
>                 URL: https://issues.apache.org/jira/browse/HBASE-7055
>             Project: HBase
>          Issue Type: Task
>          Components: Compaction
>    Affects Versions: 0.96.0
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>             Fix For: 0.96.0
>
>         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
>
>
> There's divergence in the code :(
> 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