[
https://issues.apache.org/jira/browse/HBASE-7055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540176#comment-13540176
]
Jimmy Xiang commented on HBASE-7055:
------------------------------------
I like the idea of this feature. I think it is useful. However, I am not sure
how to use it, for example, how many tiers a region should have, how to
separate each tier, and why?
This patch introduces several configuration parameters to separate tiers. Do
we have a guideline on how to use these parameters? What kind tier separation
will make the compaction scheduling efficient? If the tiers are not set
properly, could it make things even worse instead?
By the tier term, the existing compaction selection has just one tier. Can we
automatically skip the most recent storefile till we get a valid selection? By
this way, we can have dynamical tiers which guarantees some valid selection?
> 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
>
>
> 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
