hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "chenning (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7949) Enable big content store in HBase
Date Fri, 08 Mar 2013 07:44:16 GMT

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

chenning commented on HBASE-7949:
---------------------------------

[~maryannxue]thanks for the sides on this issue. 

I have one question -- why the content for lob family still goes into memstore and flushed
into HDFS? Since I think the content will occupy more memory and result in more frequent flushes
and minor compactions? 

My idea is to persisted the content directly into HDFS, but maybe this will involve more complexities
in regionserver to handle the consistency, the orphans, and row atomic etc.
                
> Enable big content store in HBase
> ---------------------------------
>
>                 Key: HBASE-7949
>                 URL: https://issues.apache.org/jira/browse/HBASE-7949
>             Project: HBase
>          Issue Type: Brainstorming
>            Reporter: chenning
>         Attachments: HBase_LOB.pdf
>
>
> Big content stored in hbase consumes a lot of system resource when region split or compaction
operation happens.
> How HBase can be used to store big content along with some self descriptive meta-data.

> The general idea is to add a new type of column family, and the content of this kind
of column family doesn't participate the region split and compaction. An index(rowkey-location)
is introduced in this new column family and the split and compaction are only applied to this
index.

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

Mime
View raw message