hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Bortnikov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17294) External Configuration for Memory Compaction
Date Mon, 19 Dec 2016 22:08:58 GMT

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

Edward Bortnikov commented on HBASE-17294:
------------------------------------------

[~devaraj], please see the performance benchmarks results reported in HBASE-16417. We started
writing a separate blog post with clearer and more concise description. Thanks. 

> External Configuration for Memory Compaction 
> ---------------------------------------------
>
>                 Key: HBASE-17294
>                 URL: https://issues.apache.org/jira/browse/HBASE-17294
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Eshcar Hillel
>            Assignee: Eshcar Hillel
>             Fix For: 2.0.0
>
>         Attachments: HBASE-17294-V01.patch, HBASE-17294-V02.patch, HBASE-17294-V03.patch
>
>
> We would like to have a single external knob to control memstore compaction.
> Possible memstore compaction policies are none, basic, and eager.
> This sub-task allows to set this property at the column family level at table creation
time:
> {code}
> create ‘<tablename>’,
>    {NAME => ‘<cfname>’, 
>     IN_MEMORY_COMPACTION => ‘<NONE|BASIC|EAGER>’}
> {code}
> or to set this at the global configuration level by setting the property in hbase-site.xml,
with BASIC being the default value:
> {code}
> <property>
> 	<name>hbase.hregion.compacting.memstore.type</name>
> 	<value><NONE|BASIC|EAGER></value>
> </property>
> {code}
> The values used in this property can change as memstore compaction policies evolve over
time.



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

Mime
View raw message