You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "jackylau (Jira)" <ji...@apache.org> on 2019/10/11 03:02:00 UTC
[jira] [Commented] (HBASE-11195) Potentially improve block locality
during major compaction for old regions
[ https://issues.apache.org/jira/browse/HBASE-11195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16949081#comment-16949081 ]
jackylau commented on HBASE-11195:
----------------------------------
hi [~churromorales] ，why need this sf.isMajorCompaction() condition in the code ?
> 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, 0.94.26, 0.98.10, 2.0.0
> Reporter: churro morales
> Assignee: churro morales
> Priority: Major
> Fix For: 1.0.0, 0.98.10, 0.94.27
>
> Attachments: HBASE-11195-0.94.patch, HBASE-11195-0.98.patch, HBASE-11195-0.98.v1.patch, HBASE-11195.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 nice.
> 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
(v8.3.4#803005)