You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@drill.apache.org by ts...@apache.org on 2015/05/01 20:08:28 UTC
[32/50] [abbrv] drill git commit: memory allocation > configuring
memory, separate topic
memory allocation > configuring memory, separate topic
Project: http://git-wip-us.apache.org/repos/asf/drill/repo
Commit: http://git-wip-us.apache.org/repos/asf/drill/commit/bf05a8e3
Tree: http://git-wip-us.apache.org/repos/asf/drill/tree/bf05a8e3
Diff: http://git-wip-us.apache.org/repos/asf/drill/diff/bf05a8e3
Branch: refs/heads/gh-pages
Commit: bf05a8e383a973c743489325ce39bd13d9709727
Parents: a4264b9
Author: Kristine Hahn <kh...@maprtech.com>
Authored: Thu Apr 30 10:32:52 2015 -0700
Committer: Kristine Hahn <kh...@maprtech.com>
Committed: Thu Apr 30 10:32:52 2015 -0700
----------------------------------------------------------------------
_data/docs.json | 75 ++++++++++++++++----
_docs/manage-drill/011-configuring-memory.md | 32 +++++++++
...-multi-instance-architecture-introduction.md | 2 +-
.../015-how-to-run-drill-in-a-cluster.md | 20 +-----
.../010-configuration-options-introduction.md | 29 --------
5 files changed, 97 insertions(+), 61 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/drill/blob/bf05a8e3/_data/docs.json
----------------------------------------------------------------------
diff --git a/_data/docs.json b/_data/docs.json
index 79468f4..d016d92 100644
--- a/_data/docs.json
+++ b/_data/docs.json
@@ -856,6 +856,23 @@
"title": "Configuring Connections on Windows",
"url": "/docs/configuring-connections-on-windows/"
},
+ "Configuring Memory": {
+ "breadcrumbs": [
+ {
+ "title": "Manage Drill",
+ "url": "/docs/manage-drill/"
+ }
+ ],
+ "children": [],
+ "next_title": "Multitenant and Multi-instance Architectures",
+ "next_url": "/docs/multitenant-and-multi-instance-architectures/",
+ "parent": "Manage Drill",
+ "previous_title": "Manage Drill Introduction",
+ "previous_url": "/docs/manage-drill-introduction/",
+ "relative_path": "_docs/manage-drill/011-configuring-memory.md",
+ "title": "Configuring Memory",
+ "url": "/docs/configuring-memory/"
+ },
"Configuring a Cluster for Different Workloads": {
"breadcrumbs": [
{
@@ -3381,8 +3398,8 @@
}
],
"children": [],
- "next_title": "Multitenant and Multi-instance Architectures",
- "next_url": "/docs/multitenant-and-multi-instance-architectures/",
+ "next_title": "Configuring Memory",
+ "next_url": "/docs/configuring-memory/",
"parent": "Manage Drill",
"previous_title": "Manage Drill",
"previous_url": "/docs/manage-drill/",
@@ -3397,6 +3414,23 @@
"url": "/docs/manage-drill/"
}
],
+ "children": [],
+ "next_title": "Multitenant and Multi-instance Architectures",
+ "next_url": "/docs/multitenant-and-multi-instance-architectures/",
+ "parent": "Manage Drill",
+ "previous_title": "Manage Drill Introduction",
+ "previous_url": "/docs/manage-drill-introduction/",
+ "relative_path": "_docs/manage-drill/011-configuring-memory.md",
+ "title": "Configuring Memory",
+ "url": "/docs/configuring-memory/"
+ },
+ {
+ "breadcrumbs": [
+ {
+ "title": "Manage Drill",
+ "url": "/docs/manage-drill/"
+ }
+ ],
"children": [
{
"breadcrumbs": [
@@ -3465,8 +3499,8 @@
"next_title": "Multitenant and Multi-instance Architectures Introduction",
"next_url": "/docs/multitenant-and-multi-instance-architectures-introduction/",
"parent": "Manage Drill",
- "previous_title": "Manage Drill Introduction",
- "previous_url": "/docs/manage-drill-introduction/",
+ "previous_title": "Configuring Memory",
+ "previous_url": "/docs/configuring-memory/",
"relative_path": "_docs/manage-drill/012-multitenant-and-multi-instance-architectures.md",
"title": "Multitenant and Multi-instance Architectures",
"url": "/docs/multitenant-and-multi-instance-architectures/"
@@ -3680,8 +3714,8 @@
}
],
"children": [],
- "next_title": "Multitenant and Multi-instance Architectures",
- "next_url": "/docs/multitenant-and-multi-instance-architectures/",
+ "next_title": "Configuring Memory",
+ "next_url": "/docs/configuring-memory/",
"parent": "Manage Drill",
"previous_title": "Manage Drill",
"previous_url": "/docs/manage-drill/",
@@ -3836,8 +3870,8 @@
"next_title": "Multitenant and Multi-instance Architectures Introduction",
"next_url": "/docs/multitenant-and-multi-instance-architectures-introduction/",
"parent": "Manage Drill",
- "previous_title": "Manage Drill Introduction",
- "previous_url": "/docs/manage-drill-introduction/",
+ "previous_title": "Configuring Memory",
+ "previous_url": "/docs/configuring-memory/",
"relative_path": "_docs/manage-drill/012-multitenant-and-multi-instance-architectures.md",
"title": "Multitenant and Multi-instance Architectures",
"url": "/docs/multitenant-and-multi-instance-architectures/"
@@ -10915,8 +10949,8 @@
}
],
"children": [],
- "next_title": "Multitenant and Multi-instance Architectures",
- "next_url": "/docs/multitenant-and-multi-instance-architectures/",
+ "next_title": "Configuring Memory",
+ "next_url": "/docs/configuring-memory/",
"parent": "Manage Drill",
"previous_title": "Manage Drill",
"previous_url": "/docs/manage-drill/",
@@ -10931,6 +10965,23 @@
"url": "/docs/manage-drill/"
}
],
+ "children": [],
+ "next_title": "Multitenant and Multi-instance Architectures",
+ "next_url": "/docs/multitenant-and-multi-instance-architectures/",
+ "parent": "Manage Drill",
+ "previous_title": "Manage Drill Introduction",
+ "previous_url": "/docs/manage-drill-introduction/",
+ "relative_path": "_docs/manage-drill/011-configuring-memory.md",
+ "title": "Configuring Memory",
+ "url": "/docs/configuring-memory/"
+ },
+ {
+ "breadcrumbs": [
+ {
+ "title": "Manage Drill",
+ "url": "/docs/manage-drill/"
+ }
+ ],
"children": [
{
"breadcrumbs": [
@@ -10999,8 +11050,8 @@
"next_title": "Multitenant and Multi-instance Architectures Introduction",
"next_url": "/docs/multitenant-and-multi-instance-architectures-introduction/",
"parent": "Manage Drill",
- "previous_title": "Manage Drill Introduction",
- "previous_url": "/docs/manage-drill-introduction/",
+ "previous_title": "Configuring Memory",
+ "previous_url": "/docs/configuring-memory/",
"relative_path": "_docs/manage-drill/012-multitenant-and-multi-instance-architectures.md",
"title": "Multitenant and Multi-instance Architectures",
"url": "/docs/multitenant-and-multi-instance-architectures/"
http://git-wip-us.apache.org/repos/asf/drill/blob/bf05a8e3/_docs/manage-drill/011-configuring-memory.md
----------------------------------------------------------------------
diff --git a/_docs/manage-drill/011-configuring-memory.md b/_docs/manage-drill/011-configuring-memory.md
new file mode 100644
index 0000000..9058cdb
--- /dev/null
+++ b/_docs/manage-drill/011-configuring-memory.md
@@ -0,0 +1,32 @@
+---
+title: "Configuring Memory"
+parent: "Manage Drill"
+---
+
+You can configure the amount of direct memory allocated to a Drillbit for
+query processing. The default limit is 8G, but Drill prefers 16G or more
+depending on the workload. The total amount of direct memory that a Drillbit
+allocates to query operations cannot exceed the limit set.
+
+Drill mainly uses Java direct memory and performs well when executing
+operations in memory instead of storing the operations on disk. Drill does not
+write to disk unless absolutely necessary, unlike MapReduce where everything
+is written to disk during each phase of a job.
+
+The JVM’s heap memory does not limit the amount of direct memory available in
+a Drillbit. The on-heap memory for Drill is only about 4-8G, which should
+suffice because Drill avoids having data sit in heap memory.
+
+## Modifying Drillbit Memory
+
+You can modify memory for each Drillbit node in your cluster. To modify the
+memory for a Drillbit, edit the `XX:MaxDirectMemorySize` parameter in the
+Drillbit startup script located in `<drill_installation_directory>/conf/drill-
+env.sh`.
+
+{% include startnote.html %}If this parameter is not set, the limit depends on the amount of available system memory.{% include endnote.html %}
+
+After you edit `<drill_installation_directory>/conf/drill-env.sh`, [restart
+the Drillbit
+]({{ site.baseurl }}/docs/starting-stopping-drill#starting-a-drillbit)on
+the node.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/drill/blob/bf05a8e3/_docs/manage-drill/013-multitenant-and-multi-instance-architecture-introduction.md
----------------------------------------------------------------------
diff --git a/_docs/manage-drill/013-multitenant-and-multi-instance-architecture-introduction.md b/_docs/manage-drill/013-multitenant-and-multi-instance-architecture-introduction.md
index 33c0b98..c517586 100644
--- a/_docs/manage-drill/013-multitenant-and-multi-instance-architecture-introduction.md
+++ b/_docs/manage-drill/013-multitenant-and-multi-instance-architecture-introduction.md
@@ -15,7 +15,7 @@ Drill typically runs along side many application frameworks, including the follo
You need to plan and configure these resources for use with Drill in a multitenant or multi-instance environment:
-* [Memory]()
+* [Memory]({{site.baseurl}}/docs/configuring-memory)
* [CPU]({{site.baseurl}}/docs/how-to-manage-drill-cpu-resources)
* Disk
http://git-wip-us.apache.org/repos/asf/drill/blob/bf05a8e3/_docs/manage-drill/015-how-to-run-drill-in-a-cluster.md
----------------------------------------------------------------------
diff --git a/_docs/manage-drill/015-how-to-run-drill-in-a-cluster.md b/_docs/manage-drill/015-how-to-run-drill-in-a-cluster.md
index f407bdb..d8609c5 100644
--- a/_docs/manage-drill/015-how-to-run-drill-in-a-cluster.md
+++ b/_docs/manage-drill/015-how-to-run-drill-in-a-cluster.md
@@ -23,25 +23,7 @@ To run Drill in a MapR cluster, allocate memory by configuring settings in warde
### Drill Memory
You can configure the amount of direct memory allocated to a Drillbit for
-query processing. The default limit is 8G, but Drill prefers 16G or more
-depending on the workload. The total amount of direct memory that a Drillbit
-allocates to query operations cannot exceed the limit set.
-
-Drill mainly uses Java direct memory and performs well when executing
-operations in memory instead of storing the operations on disk. Drill does not
-write to disk unless absolutely necessary, unlike MapReduce where everything
-is written to disk during each phase of a job.
-
-The JVM’s heap memory does not limit the amount of direct memory available in
-a Drillbit. The on-heap memory for Drill is only about 4-8G, which should
-suffice because Drill avoids having data sit in heap memory.
-
-You can modify memory for each Drillbit node in your cluster. To modify the
-memory for a Drillbit, edit the `XX:MaxDirectMemorySize` parameter in the
-Drillbit startup script located in `<drill_installation_directory>/conf/drill-
-env.sh`.
-
-If this parameter is not set, the limit depends on the amount of available system memory.
+query processing, as described in the section, ["Configuring Memory"](({{site.baseurl}}/docs/configuring-memory).
### Memory in a MapR Cluster
Memory and disk for Drill and other services that are not associated with roles on a MapR cluster are shared with other services. You manage the chunk of memory for these services in os heap settings in `warden.conf` and in configuration files of the particular service. The warden os heap settings are:
http://git-wip-us.apache.org/repos/asf/drill/blob/bf05a8e3/_docs/manage-drill/configuration-options/010-configuration-options-introduction.md
----------------------------------------------------------------------
diff --git a/_docs/manage-drill/configuration-options/010-configuration-options-introduction.md b/_docs/manage-drill/configuration-options/010-configuration-options-introduction.md
index ab5370b..e49b17a 100644
--- a/_docs/manage-drill/configuration-options/010-configuration-options-introduction.md
+++ b/_docs/manage-drill/configuration-options/010-configuration-options-introduction.md
@@ -405,32 +405,3 @@ The sys.options table lists the following options that you can set at the sessio
\* Not supported in this release.
-## Memory Allocation
-
-You can configure the amount of direct memory allocated to a Drillbit for
-query processing. The default limit is 8G, but Drill prefers 16G or more
-depending on the workload. The total amount of direct memory that a Drillbit
-allocates to query operations cannot exceed the limit set.
-
-Drill mainly uses Java direct memory and performs well when executing
-operations in memory instead of storing the operations on disk. Drill does not
-write to disk unless absolutely necessary, unlike MapReduce where everything
-is written to disk during each phase of a job.
-
-The JVM’s heap memory does not limit the amount of direct memory available in
-a Drillbit. The on-heap memory for Drill is only about 4-8G, which should
-suffice because Drill avoids having data sit in heap memory.
-
-## Modifying Drillbit Memory
-
-You can modify memory for each Drillbit node in your cluster. To modify the
-memory for a Drillbit, edit the `XX:MaxDirectMemorySize` parameter in the
-Drillbit startup script located in `<drill_installation_directory>/conf/drill-
-env.sh`.
-
-{% include startnote.html %}If this parameter is not set, the limit depends on the amount of available system memory.{% include endnote.html %}
-
-After you edit `<drill_installation_directory>/conf/drill-env.sh`, [restart
-the Drillbit
-]({{ site.baseurl }}/docs/starting-stopping-drill#starting-a-drillbit)on
-the node.
\ No newline at end of file