hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16417) In-Memory MemStore Policy for Flattening and Compactions
Date Tue, 28 Feb 2017 16:51:46 GMT

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

ramkrishna.s.vasudevan commented on HBASE-16417:

What is the size of each KV? Are you doing YCSB or PE?
bq.Could it be due to double logging of the same information?
I don't think so. But not sure. I think depends on your cell size though value is 100B only.
bq.Here the sizes of the files vary, NONE/BASIC write roughly 850 files, EAGER roughly 480.
Something to check. Async mode as per our experiments were bit slower and had some bugs that
[~Apache9] fixed. But I don't think we had any data loss there. Can check once.

> 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

View raw message