hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11195) Potentially improve block locality during major compaction for old regions
Date Fri, 16 Jan 2015 18:36:35 GMT

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

Andrew Purtell commented on HBASE-11195:

I think in the refactored else clause of {{if (sf.isMajorCompaction() && (cfTtl ==
HConstants.FOREVER || oldest < cfTtl))}} we should amend the DEBUG level log to also print
the locality, since it's a factor in the decision now. Will make that trivial change upon

> Potentially improve block locality during major compaction for old regions
> --------------------------------------------------------------------------
>                 Key: HBASE-11195
>                 URL: https://issues.apache.org/jira/browse/HBASE-11195
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 1.0.0, 2.0.0, 0.94.26, 0.98.10
>            Reporter: churro morales
>            Assignee: churro morales
>         Attachments: HBASE-11195-0.94.patch, HBASE-11195-0.98.patch, HBASE-11195.patch
> This might be a specific use case.  But we have some regions which are no longer written
to (due to the key).  Those regions have 1 store file and they are very old, they haven't
been written to in a while.  We still use these regions to read from so locality would be
> I propose putting a configuration option: something like
> hbase.hstore.min.locality.to.skip.major.compact [between 0 and 1]
> such that you can decide whether or not to skip major compaction for an old region with
a single store file.
> I'll attach a patch, let me know what you guys think.

This message was sent by Atlassian JIRA

View raw message