You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Michael Brown (JIRA)" <ji...@apache.org> on 2018/01/25 02:00:03 UTC

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

Michael Brown created IMPALA-6441:
-------------------------------------

             Summary: 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


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)