hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eshcar Hillel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16417) In-Memory MemStore Policy for Flattening and Compactions
Date Sun, 12 Feb 2017 12:09:42 GMT

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

Eshcar Hillel commented on HBASE-16417:
---------------------------------------

Back to running large scale benchmarks !!
After some changes to the code and some bug fixes, I am now trying to re-run the ycsb benchmarks
with the most up-to-date code in master.
However I have a problem when my scripts try to initialize the table with different in-memory
compaction policies in hbase shell:
{code}
hbase(main):002:0> create 'usertable', {NAME=>'values', IN_MEMORY_COMPACTION=>NONE}
Created table usertable
Took 0.3080 seconds                                                                      
                                                                                         
hbase(main):003:0> describe 'usertable'
Table usertable is ENABLED                                                               
                                                                                         
usertable                                                                                
                                                                                         
COLUMN FAMILIES DESCRIPTION                                                              
                                                                                         
{NAME => 'values', BLOOMFILTER => 'ROW', VERSIONS => '1', IN_MEMORY => 'false',
KEEP_DELETED_CELLS => 'FALSE', DATA_BLOCK_ENCODING => 'NONE', TTL => 'FOREVER', COMPRESSION
=> 'NONE', MIN_VERSIONS => '0', BLOCKCACHE => 'true', BLOCKSIZE => '65536', REPLICATION_SCOPE
=> '0', METADATA => {'IN_MEMORY_COMPACTION' => 'NONE'}}                         
           
1 row(s)
Took 0.1670 seconds                                                                      
                                                                                         
hbase(main):004:0> disable 'usertable'
Took 1.2640 seconds                                                                      
                                                                                         
hbase(main):005:0> drop 'usertable'
Took 0.2470 seconds       
                                                                                         
                                                               
hbase(main):006:0> create 'usertable', {NAME=>'values', IN_MEMORY_COMPACTION=>BASIC}
NameError: uninitialized constant BASIC

hbase(main):007:0> create 'usertable', {NAME=>'values', IN_MEMORY_COMPACTION=>EAGER}
NameError: uninitialized constant EAGER
{code}

We have tried to make this work in HBASE-17492 but it seems that we need some help to get
this right once and for all.

questions:
(1) Why does IN_MEMORY_COMPACTION is classified as METADATA?
(2) How come the table is initialized with NONE while EAGER and BASIC are uninitialized, where
all three are defined in one enum structure?

Anyone can help us understand what we are doing wrong in the ruby script?

> In-Memory MemStore Policy for Flattening and Compactions
> --------------------------------------------------------
>
>                 Key: HBASE-16417
>                 URL: https://issues.apache.org/jira/browse/HBASE-16417
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Anastasia Braginsky
>            Assignee: Eshcar Hillel
>             Fix For: 2.0.0
>
>         Attachments: HBASE-16417-benchmarkresults-20161101.pdf, HBASE-16417-benchmarkresults-20161110.pdf,
HBASE-16417-benchmarkresults-20161123.pdf, HBASE-16417-benchmarkresults-20161205.pdf
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message