Uploaded image for project: 'Apache Drill'
  1. Apache Drill
  2. DRILL-6513

Drill should only allow valid values when users set planner.memory.max_query_memory_per_node

    Details

      Description

      The "planner.memory.max_query_memory_per_node" configuration can be currently set to values higher than the Drillbit Direct Memory configuration. The goal of this Jira is to fail queries with such an erroneous configuration to avoid runtime OOM.

      NOTE - The current semantic of the maximum query memory per node configuration is that the end user has computed valid values especially knowing the current Drill limitations. Such values have to account for Netty's overhead (memory pools), shared pools (e.g., network exchanges), and concurrent query execution. This Jira should not be used to also cover such use-cases. The Drill Resource Management feature has the means to automate query quotas and the associated validation. We should create another Jira requesting the enhanced validations contracts under the umbrella of the Resource Management feature.   

       

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                sachouche salim achouche
                Reporter:
                sachouche salim achouche
                Reviewer:
                Timothy Farkas
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: