Repository: drill Updated Branches: refs/heads/gh-pages bc608f5a2 -> 8714fc807
instructions for last-modified-date typos Project: http://git-wip-us.apache.org/repos/asf/drill/repo Commit: http://git-wip-us.apache.org/repos/asf/drill/commit/8714fc80 Tree: http://git-wip-us.apache.org/repos/asf/drill/tree/8714fc80 Diff: http://git-wip-us.apache.org/repos/asf/drill/diff/8714fc80 Branch: refs/heads/gh-pages Commit: 8714fc8079e4810068c75582d14647245f422d1a Parents: bc608f5 Author: Kris Hahn <krish...@apache.org> Authored: Mon Dec 28 17:11:58 2015 -0800 Committer: Kris Hahn <krish...@apache.org> Committed: Mon Dec 28 17:16:51 2015 -0800 ---------------------------------------------------------------------- README.md | 25 ++++++++++++++++++++ .../050-configuring-multitenant-resources.md | 9 +++---- 2 files changed, 30 insertions(+), 4 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/drill/blob/8714fc80/README.md ---------------------------------------------------------------------- diff --git a/README.md b/README.md index 56d6cb6..2fdc1e4 100644 --- a/README.md +++ b/README.md @@ -11,6 +11,31 @@ jekyll serve --config _config.yml,_config-prod.yml ``` Note that you can skip the first two commands (and only run `jekyll serve`) if you haven't changed the title or path of any of the documentation pages. +To automatically add the last-modified-on date, a one-time local setup is required: + +1. In your cloned directory of Drill, in drill/.git/hooks, create a file named pre-commit (no extension) that contains this script: + + #!/bin/sh + # Contents of .git/hooks/pre-commit + + git diff --cached --name-status | grep "^M" | while read a b; do + cat $b | sed "/---.*/,/---.*/s/^date:.*$/date: $(date -u "+%Y-%m-%d %T %Z")/" > tmp + mv tmp $b + git add $b + done + +2. Make the file executable. + + chmod +x pre-commit + +In addition the title: and parent:, add date: to the front matter of any file you create. For example: + + --- + title: "Configuring Multitenant Resources" + parent: "Configuring a Multitenant Cluster" + date: + --- + # Compiling the Website Once the website is ready, you'll need to compile the site to static HTML so that it can then be published to Apache. This is as simple as running the `jekyll build` command. The _config-prod.yml configuration file causes a few changes to the site: http://git-wip-us.apache.org/repos/asf/drill/blob/8714fc80/_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 d6fdeba..f9e935d 100644 --- a/_docs/configure-drill/050-configuring-multitenant-resources.md +++ b/_docs/configure-drill/050-configuring-multitenant-resources.md @@ -1,20 +1,21 @@ --- title: "Configuring Multitenant Resources" -date: +date: 2015-12-29 01:12:25 UTC 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 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 +## Configuring Drill in a YARN-enabled cluster -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: +To add Drill to a YARN-enabled cluster, change memory resources to suit your application. For example, you have 128G of available memory that you allocate to following workloads in a Yarn-enabled cluster: File system = 20G HBase = 20G -Yarn = 20G OS = 8G +Yarn = ? +Drill = ? If Yarn does most of the work, give Drill 20G, for example, and give Yarn 60G. If you expect a heavy query load, give Drill 60G and Yarn 20G.
