[jira] [Comment Edited] (PHOENIX-5336) Speed up MutableIndexSplitForwardScanIT and MutableIndexSplitReverseScanIT

["Lars Hofhansl (JIRA)" <ji...@apache.org>]

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

Lars Hofhansl edited comment on PHOENIX-5336 at 6/15/19 5:26 AM:
-----------------------------------------------------------------

-v2 works. (Verified in -1.3, -1.5, and master).

The problem before was that a split would fail when a prior split was not finished yet (NSRE with -1.3, and region not splittable error in master).
A split typically take about 1-2 seconds or so. As a safety measure against runaway tests, I limit how long we retry any consecutive split to 60s.

Please have a look. This too cuts the runtime from 13m (I said 17m above, but it's actually 13m) to 2m on my box.



was (Author: lhofhansl):
-v2 works. (Verified in -1.3, -1.5, and master).

The problem before was that a split would fail when a prior split was not finished yet (NSRE with -1.3, and region not splittable error in master).
A split typically take about 1-2 seconds or so. As a safety measure against runaway tests, I limit how long we retry any consecutive split to 60s.

Please have a look. This too cuts the runtime from 17m to 2m on my box.


> Speed up MutableIndexSplitForwardScanIT and MutableIndexSplitReverseScanIT
> --------------------------------------------------------------------------
>
>                 Key: PHOENIX-5336
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5336
>             Project: Phoenix
>          Issue Type: Sub-task
>    Affects Versions: 4.15.0, 5.1.0
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>            Priority: Major
>         Attachments: 5336-v2-master.txt, 5336-v2.txt, 5336.txt
>
>
> I observed that these tests are slow because we wait after the split until the parent has been compacted away. It's not necessary to do so (unless we wanted to test that specific HBase logic and HBase already has many tests for that). We can change the test to only wait until the daughter regions are created. When they exist they will be used.
> Avoiding that waiting cuts the runtime of each test from 17mins to 2min (on my machine) so it saves at least 30mins of runtime (and more on the slower jenkins machines)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)