You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@drill.apache.org by br...@apache.org on 2017/08/17 22:51:54 UTC
drill-site git commit: minor edit
Repository: drill-site
Updated Branches:
refs/heads/asf-site 7ecab1e6e -> e3d8bad1b
minor edit
Project: http://git-wip-us.apache.org/repos/asf/drill-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/drill-site/commit/e3d8bad1
Tree: http://git-wip-us.apache.org/repos/asf/drill-site/tree/e3d8bad1
Diff: http://git-wip-us.apache.org/repos/asf/drill-site/diff/e3d8bad1
Branch: refs/heads/asf-site
Commit: e3d8bad1bee6b57e43da969f843218150754d3b3
Parents: 7ecab1e
Author: Bridget Bevens <bb...@maprtech.com>
Authored: Thu Aug 17 15:51:38 2017 -0700
Committer: Bridget Bevens <bb...@maprtech.com>
Committed: Thu Aug 17 15:51:38 2017 -0700
----------------------------------------------------------------------
docs/configuration-options-introduction/index.html | 2 +-
.../index.html | 2 +-
feed.xml | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/drill-site/blob/e3d8bad1/docs/configuration-options-introduction/index.html
----------------------------------------------------------------------
diff --git a/docs/configuration-options-introduction/index.html b/docs/configuration-options-introduction/index.html
index 2808872..6be9503 100644
--- a/docs/configuration-options-introduction/index.html
+++ b/docs/configuration-options-introduction/index.html
@@ -1414,7 +1414,7 @@
<tr>
<td>planner.memory.max_query_memory_per_node</td>
<td>2147483648 bytes</td>
-<td>Sets the maximum amount of direct memory allocated to the Sort and Hash Aggregate operators during each query on a node. This memory is split between operators. If a query plan contains multiple Sort and/or Hash Aggregate operators, the memory is divided between them. The default setting is very conservative.</td>
+<td>Sets the maximum amount of direct memory allocated to the Sort and Hash Aggregate operators during each query on a node. This memory is split between operators. If a query plan contains multiple Sort and/or Hash Aggregate operators, the memory is divided between them. The default setting is too small for queries on large data sets and should be increased.</td>
</tr>
<tr>
<td>planner.memory.non_blocking_operators_memory</td>
http://git-wip-us.apache.org/repos/asf/drill-site/blob/e3d8bad1/docs/sort-based-and-hash-based-memory-constrained-operators/index.html
----------------------------------------------------------------------
diff --git a/docs/sort-based-and-hash-based-memory-constrained-operators/index.html b/docs/sort-based-and-hash-based-memory-constrained-operators/index.html
index fd10d3b..c1d1a67 100644
--- a/docs/sort-based-and-hash-based-memory-constrained-operators/index.html
+++ b/docs/sort-based-and-hash-based-memory-constrained-operators/index.html
@@ -1140,7 +1140,7 @@
<h2 id="memory-options">Memory Options</h2>
-<p>The <code>planner.memory.max_query_memory_per_node</code> option sets the maximum amount of direct memory allocated to the Sort and Hash Aggregate operators during each query on a node. The default limit is 2147483648 bytes (2GB), which is quite conservative. This memory is split between operators. If a query plan contains multiple Sort and/or Hash Aggregate operators, the memory is divided between them.</p>
+<p>The <code>planner.memory.max_query_memory_per_node</code> option sets the maximum amount of direct memory allocated to the Sort and Hash Aggregate operators during each query on a node. The default limit is set to 2147483648 bytes (2GB), which is too small for queries on large data sets and should be increased. This memory is split between operators. If a query plan contains multiple Sort and/or Hash Aggregate operators, the memory is divided between them.</p>
<p>When a query is parallelized, the number of operators is multiplied, which reduces the amount of memory given to each instance of the Sort and Hash Aggregate operators during a query. If you encounter memory issues when running queries with Sort and Hash Aggregate operators, calculate the memory requirements for your queries and the amount of available memory on each node. Based on the information, increase the value of the <code>planner.memory.max_query_memory_per_node</code> option using the ALTER SYSTEM|SESSION SET command, as shown: </p>
<div class="highlight"><pre><code class="language-text" data-lang="text">ALTER SYSTEM|SESSION SET `planner.memory.max_query_memory_per_node` = <new_value>
http://git-wip-us.apache.org/repos/asf/drill-site/blob/e3d8bad1/feed.xml
----------------------------------------------------------------------
diff --git a/feed.xml b/feed.xml
index 764491a..ed03ac0 100644
--- a/feed.xml
+++ b/feed.xml
@@ -6,8 +6,8 @@
</description>
<link>/</link>
<atom:link href="/feed.xml" rel="self" type="application/rss+xml"/>
- <pubDate>Thu, 17 Aug 2017 14:50:10 -0700</pubDate>
- <lastBuildDate>Thu, 17 Aug 2017 14:50:10 -0700</lastBuildDate>
+ <pubDate>Thu, 17 Aug 2017 15:49:16 -0700</pubDate>
+ <lastBuildDate>Thu, 17 Aug 2017 15:49:16 -0700</lastBuildDate>
<generator>Jekyll v2.5.2</generator>
<item>