[jira] [Resolved] (IMPALA-6441) concurrent select binary search explain string pattern match is wrong

["Michael Brown (JIRA)" <ji...@apache.org>]

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

Michael Brown resolved IMPALA-6441.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.0

> concurrent select binary search explain string pattern match is wrong
> ---------------------------------------------------------------------
>
>                 Key: IMPALA-6441
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6441
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Infrastructure
>    Affects Versions: Impala 2.9.0
>            Reporter: Michael Brown
>            Assignee: Michael Brown
>            Priority: Major
>             Fix For: Impala 3.0
>
>
> The pattern match for finding a start point in the stress test's binary search was based on the explain output, and after memory reservations, was never updated. It had a silent failsafe path and chose the memory limit of impalad as a start point instead. This means the binary search, while known to take a long time, is certainly taking longer than it should.
> The current pattern is:
> {noformat}
> MEM_ESTIMATE_PATTERN = re.compile(r"Estimated.*Memory=(\d+.?\d*)(T|G|M|K)?B")
> {noformat}
> [~tarmstrong] can you confirm we need to match on the second line here?
> {noformat}
> Max Per-Host Resource Reservation: Memory=156.88MB
> Per-Host Resource Estimates: Memory=14.67GB
> {noformat}



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