You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2019/10/07 18:30:01 UTC

[jira] [Updated] (HBASE-21520) TestMultiColumnScanner cost long time when using ROWCOL bloom type

     [ https://issues.apache.org/jira/browse/HBASE-21520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Kyle Purtell updated HBASE-21520:
----------------------------------------
    Fix Version/s:     (was: 1.5.0)

> TestMultiColumnScanner cost long time when using ROWCOL bloom type
> ------------------------------------------------------------------
>
>                 Key: HBASE-21520
>                 URL: https://issues.apache.org/jira/browse/HBASE-21520
>             Project: HBase
>          Issue Type: Improvement
>          Components: test
>            Reporter: Zheng Hu
>            Assignee: Zheng Hu
>            Priority: Major
>             Fix For: 3.0.0, 2.2.0, 2.1.2, 1.2.10, 1.4.10, 2.0.5
>
>         Attachments: HBASE-21520.branch-1.v4.patch, HBASE-21520.v1.patch, HBASE-21520.v2.patch, HBASE-21520.v3.patch, HBASE-21520.v4.patch, TestMultiColumnScanner.png, rowcol.txt
>
>
> The TestMultiColumnScanner is easy to be timeout,  you can see HBASE-21517.   In my localhost,  when I set the parameters to be { Compression.Algorithm.NONE, BloomType.ROW, false },  it took about 5 seconds.  but if I set the parameters to be  { Compression.Algorithm.NONE, BloomType.ROWCOL, false },  it would take about 45 seconds, which means ROWCOL cost much more time than ROW.
> Need to find out what's wrong with this ut.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)