Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Sat, 11 Apr 2015 01:11:13 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12540461.1327968198000.60952.1428714673588@Atlassian.JIRA>
In-Reply-To: <JIRA.12540461.1327968198000@Atlassian.JIRA>
References: <JIRA.12540461.1327968198000@Atlassian.JIRA>
 <JIRA.12540461.1327968198282@arcas>
Subject: [jira] [Resolved] (HBASE-5303) Separate out rows into multiple
 files during compaction for better block cache utilization
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Purtell resolved HBASE-5303.
-----------------------------------
    Resolution: Incomplete
      Assignee:     (was: dhruba borthakur)

> Separate out rows into multiple files during compaction for better block cache utilization
> ------------------------------------------------------------------------------------------
>
>                 Key: HBASE-5303
>                 URL: https://issues.apache.org/jira/browse/HBASE-5303
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>            Reporter: dhruba borthakur
>
> This seems odd at first sight, a compaction is supposed to reduce the number of files. But there is great advantage to creating hbase blocks where adjacent keys are accessed together. One approach would be to make compaction write out hot-rows into one file and the cold-rows into another file. This increases the efficiency of the block cache because only the blocks in the hot-rows file will most frequently be populated in the block cache.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)