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/12 07:56:47 UTC
[05/25] drill git commit: more mapr stuff removed
more mapr stuff removed
Project: http://git-wip-us.apache.org/repos/asf/drill/repo
Commit: http://git-wip-us.apache.org/repos/asf/drill/commit/ef3572bf
Tree: http://git-wip-us.apache.org/repos/asf/drill/tree/ef3572bf
Diff: http://git-wip-us.apache.org/repos/asf/drill/diff/ef3572bf
Branch: refs/heads/gh-pages
Commit: ef3572bfcf7ff42de34bb51d565ac9096e998013
Parents: 913b998
Author: Kristine Hahn <kh...@maprtech.com>
Authored: Thu May 7 16:16:13 2015 -0700
Committer: Kristine Hahn <kh...@maprtech.com>
Committed: Thu May 7 16:16:13 2015 -0700
----------------------------------------------------------------------
.../050-configuring-multitenant-resources.md | 13 +++----------
1 file changed, 3 insertions(+), 10 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/drill/blob/ef3572bf/_docs/configure-drill/050-configuring-multitenant-resources.md
----------------------------------------------------------------------
diff --git a/_docs/configure-drill/050-configuring-multitenant-resources.md b/_docs/configure-drill/050-configuring-multitenant-resources.md
index 2acd0e7..fcdab5c 100644
--- a/_docs/configure-drill/050-configuring-multitenant-resources.md
+++ b/_docs/configure-drill/050-configuring-multitenant-resources.md
@@ -2,11 +2,11 @@
title: "Configuring Multitenant Resources"
parent: "Configuring a Multitenant Cluster"
---
-Drill operations are memory and CPU-intensive. Currently, Drill resources are managed outside of any cluster management service. In a multitenant or any other type of cluster, YARN-enabled or not, you configure memory and memory usage limits for Drill by modifying drill-env.sh as described in ["Configuring Drill Memory"]({{site.baseurl}}/docs/configuring-drill-memory).
+Drill operations are memory and CPU-intensive. Currently, Drill resources are managed outside of any cluster management service. In a multitenant or any other type of cluster, YARN-enabled or not, you configure memory and memory usage limits for Drill by modifying the `drill-env.sh` file as described in ["Configuring Drill Memory"]({{site.baseurl}}/docs/configuring-drill-memory).
Configure a multitenant cluster manager to account for resources required for Drill. Configuring `drill-env.sh` allocates resources for Drill to use during query execution. It might be necessary to configure the cluster manager from committing the resources to other processes.
-## Configuring Drill in a YARN-enabled MapR Cluster
+## Configuring Drill in a YARN-enabled
To add Drill to a YARN-enabled cluster, change memory resources to suit your application. For example, you have 120G of available memory that you allocate to following workloads in a Yarn-enabled cluster:
@@ -26,14 +26,7 @@ YARN consists of two main services:
* NodeManager
There is one instance per node.
-ResourceManager and NodeManager memory in `warden.resourcemanager.conf` and
- `warden.nodemanager.conf` are set to the following defaults.
-
- service.heapsize.min=64
- service.heapsize.max=325
- service.heapsize.percent=2
-
-Change these settings for NodeManager and ResourceManager to reconfigure the total memory required for YARN services to run. If you want to place an upper limit on memory set YARN_NODEMANAGER_HEAPSIZE or YARN_RESOURCEMANAGER_HEAPSIZE environment variable. Do not set the `-Xmx` option to allow the heap to grow as needed.
+Configure NodeManager and ResourceManager to reconfigure the total memory required for YARN services to run. If you want to place an upper limit on memory set YARN_NODEMANAGER_HEAPSIZE or YARN_RESOURCEMANAGER_HEAPSIZE environment variable. Do not set the `-Xmx` option to allow the heap to grow as needed.
### MapReduce Resources