hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14061) Support CF-level Storage Policy
Date Tue, 10 Jan 2017 15:15:58 GMT

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

Sean Busbey commented on HBASE-14061:
-------------------------------------

Addendum looks good, I can confirm that the hadoop profile 3 works locally for me with it,
as well as Hadoop 2.6.1 and 2.7.1.

I'd recommend updating references to "Hadoop 2.8.0+" to say "Hadoop 2.8.0+ / 3.0.0-alpha1+",
because the latter came out before Hadoop 2.8.0 and future releases on the Hadoop 3.y line
don't have any particular time relationship to future Hadoop 2.w releases.

> Support CF-level Storage Policy
> -------------------------------
>
>                 Key: HBASE-14061
>                 URL: https://issues.apache.org/jira/browse/HBASE-14061
>             Project: HBase
>          Issue Type: Sub-task
>          Components: HFile, regionserver
>         Environment: hadoop-2.6.0
>            Reporter: Victor Xu
>            Assignee: Yu Li
>             Fix For: 2.0.0
>
>         Attachments: HBASE-14061-master-v1.patch, HBASE-14061.addendum.patch, HBASE-14061.addendum.patch,
HBASE-14061.v2.patch, HBASE-14061.v3.patch, HBASE-14061.v4.patch
>
>
> After reading [HBASE-12848|https://issues.apache.org/jira/browse/HBASE-12848] and [HBASE-12934|https://issues.apache.org/jira/browse/HBASE-12934],
I wrote a patch to implement cf-level storage policy. 
> My main purpose is to improve random-read performance for some really hot data, which
usually locates in certain column family of a big table.
> Usage:
> $ hbase shell
> > alter 'TABLE_NAME', METADATA => {'hbase.hstore.block.storage.policy' => 'POLICY_NAME'}
> > alter 'TABLE_NAME', {NAME=>'CF_NAME', METADATA => {'hbase.hstore.block.storage.policy'
=> 'POLICY_NAME'}}
> HDFS's setStoragePolicy can only take effect when new hfile is created in a configured
directory, so I had to make sub directories(for each cf) in region's .tmp directory and set
storage policy for them.
> Besides, I had to upgrade hadoop version to 2.6.0 because dfs.getStoragePolicy cannot
be easily written in reflection, and I needed this api to finish my unit test.



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

Mime
View raw message