Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-6441

concurrent select binary search explain string pattern match is wrong

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: Impala 2.9.0
    • Fix Version/s: Impala 3.0
    • Component/s: Infrastructure
    • Labels:
      None
    • Target Version:
    • Epic Color:
      ghx-label-6

      Description

      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:

      MEM_ESTIMATE_PATTERN = re.compile(r"Estimated.*Memory=(\d+.?\d*)(T|G|M|K)?B")

      Tim Armstrong can you confirm we need to match on the second line here?

      Max Per-Host Resource Reservation: Memory=156.88MB
Per-Host Resource Estimates: Memory=14.67GB

        Attachments

          Issue Links

          breaks

          Bug - A problem which impairs or prevents the functions of the product. IMPALA-6447 Failure in tests.stress.concurrent_select

          • Blocker - Blocks development and/or testing work, production could not run
          • Resolved

            Activity

              People

              • Assignee:
                mikeb Michael Brown
                Reporter:
                mikeb Michael Brown
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: