You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2013/06/19 02:18:20 UTC

[jira] [Resolved] (HBASE-8765) split should be based on store size, not HFile size

     [ https://issues.apache.org/jira/browse/HBASE-8765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Shelukhin resolved HBASE-8765.
-------------------------------------

    Resolution: Invalid
    
> split should be based on store size, not HFile size
> ---------------------------------------------------
>
>                 Key: HBASE-8765
>                 URL: https://issues.apache.org/jira/browse/HBASE-8765
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.95.1
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>             Fix For: 0.95.2
>
>
> I noticed that the current split behavior is rather suboptimal with regard to compactions. On large regions, HFile size limit triggers a split. Split is followed by major compaction to get rid of the partial reference files. However, HFile size limit is surpassed after compaction most of the time.
> So, first we rewrite a lot of data into a new file. Then we say "Oh look! A large file!", split the region and rewrite everything again.
> Perhaps region split should be based on store size, or incoming compaction size - large enough compaction should be converted into splits.
> Thoughts? I think basing off store size is a simple fix, and will code it up soon if there are no objections

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