hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7055) port HBASE-6371 tier-based compaction from 0.89-fb to trunk
Date Wed, 31 Oct 2012 18:08:13 GMT

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

Enis Soztutar commented on HBASE-7055:

bq. I'm guessing the separate config file is used to support runtime reloading of the tiering
strategies? Putting it in a separate config means that users won't get confused into thinking
that other properties in hbase-site are reloadable.
Makes sense, but I've seen a comment on CompactionConfiguration that indicates that it is
not there. Did not check the code though. 
 +//TODO: revisit this class for online parameter updating

>From my understanding of a skim through the patch, this is not the leveldb approach of
doing level-wise compaction with non-overlapping key ranges, but divides the candidate space
into tiers (at most 3 tiers?). Regardless, it is good that this also seem to introduce pluggable
compaction policies, but I dont think we should change the default policy without understanding
the impacts of the new algo. 

> port HBASE-6371 tier-based compaction from 0.89-fb to trunk
> -----------------------------------------------------------
>                 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
> 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

View raw message