salim achouche created DRILL-6513:
-------------------------------------
Summary: Drill should only allow valid values when users set
planner.memory.max_query_memory_per_node
Key: DRILL-6513
URL: https://issues.apache.org/jira/browse/DRILL-6513
Project: Apache Drill
Issue Type: Bug
Components: Query Planning & Optimization
Reporter: salim achouche
Assignee: salim achouche
Fix For: 1.14.0
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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
