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 Mon, 20 Mar 2017 10:13:41 GMT

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

Eshcar Hillel commented on HBASE-16417:

I can use the code of HBASE-17655 to run the mixed workload benchmark to see if parallel seek
fixes the high percentiles degradation.
However as I understand the code despite the fact that parallelSeekEnabled is set to true
when StoreScanner is created, since
isLazy = explicitColumnQuery && lazySeekEnabledGlobally
and since lazySeekEnabledGlobally is set to true by default and
explicitColumnQuery is set to numCol > 0  which is true in our case (I think it is always
true) then parallelSeek() is never invoked.
Am I missing anything? What was the original intention -- when would we not want to run parallel

> 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, HBASE-16417-benchmarkresults-20170309.pdf,

This message was sent by Atlassian JIRA

View raw message