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

limit 0; causes huge cluster_mem_estimate

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • Impala 2.3.0
    • Impala 2.5.0
    • Backend
    • None

    Description

      Some tools (e.g. Tableau) run their queries with "limit 0" first to conveniently get the list of column names.
      In this specific case the Admission control calculates cluster_mem_estimate = (number of hosts)*(rm_default_memory=4G), which can quickly allocate all the memory in the pool, causing admission timeouts while nothing is really running.

      The problem arises in admission-controller.cc GetPerHostMemoryEstimate().
      request_.per_host_mem_req is 0 in this case, which is treated as an invalid value, thus has_estimate remains false, and the logic falls back to using FLAGS_rm_default_memory, which is by default 4G.

      Attachments

        Activity

          People

            Unassigned Unassigned
            szama_impala_6295 Marcell Szabo
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: