Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 018BB200BA0 for ; Thu, 29 Sep 2016 19:22:25 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 00710160AE8; Thu, 29 Sep 2016 17:22:25 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 420BE160AF4 for ; Thu, 29 Sep 2016 19:22:23 +0200 (CEST) Received: (qmail 56009 invoked by uid 500); 29 Sep 2016 17:22:22 -0000 Mailing-List: contact commits-help@hawq.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hawq.incubator.apache.org Delivered-To: mailing list commits@hawq.incubator.apache.org Received: (qmail 55812 invoked by uid 99); 29 Sep 2016 17:22:22 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Sep 2016 17:22:22 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id C714FC61AC for ; Thu, 29 Sep 2016 17:22:21 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -6.219 X-Spam-Level: X-Spam-Status: No, score=-6.219 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 4j5JJbe4unAL for ; Thu, 29 Sep 2016 17:22:20 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with SMTP id F19465FE33 for ; Thu, 29 Sep 2016 17:22:17 +0000 (UTC) Received: (qmail 51476 invoked by uid 99); 29 Sep 2016 17:22:16 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Sep 2016 17:22:16 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 61A01EF79F; Thu, 29 Sep 2016 17:22:16 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: yozie@apache.org To: commits@hawq.incubator.apache.org Date: Thu, 29 Sep 2016 17:22:53 -0000 Message-Id: In-Reply-To: References: X-Mailer: ASF-Git Admin Mailer Subject: [39/50] [abbrv] incubator-hawq-docs git commit: VSEGMENT_RESOURCE_QUOTA to VSEG_RESOURCE_QUOTA archived-at: Thu, 29 Sep 2016 17:22:25 -0000 VSEGMENT_RESOURCE_QUOTA to VSEG_RESOURCE_QUOTA Project: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/commit/697fed81 Tree: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/tree/697fed81 Diff: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/diff/697fed81 Branch: refs/heads/master Commit: 697fed818c4b4046988794621ec9bbffaa825f4e Parents: 37857ea Author: Lisa Owen Authored: Tue Sep 27 08:42:46 2016 -0700 Committer: Lisa Owen Committed: Tue Sep 27 08:42:46 2016 -0700 ---------------------------------------------------------------------- reference/sql/ALTER-RESOURCE-QUEUE.html.md.erb | 4 ++-- reference/sql/CREATE-RESOURCE-QUEUE.html.md.erb | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/697fed81/reference/sql/ALTER-RESOURCE-QUEUE.html.md.erb ---------------------------------------------------------------------- diff --git a/reference/sql/ALTER-RESOURCE-QUEUE.html.md.erb b/reference/sql/ALTER-RESOURCE-QUEUE.html.md.erb index 16e4411..e1a31db 100644 --- a/reference/sql/ALTER-RESOURCE-QUEUE.html.md.erb +++ b/reference/sql/ALTER-RESOURCE-QUEUE.html.md.erb @@ -17,7 +17,7 @@ where \ is: [CORE_LIMIT_CLUSTER=] [ACTIVE_STATEMENTS=] [ALLOCATION_POLICY='even'] - [VSEGMENT_RESOURCE_QUOTA='mem:'] + [VSEG_RESOURCE_QUOTA='mem:'] [RESOURCE_OVERCOMMIT_FACTOR=] [NVSEG_UPPER_LIMIT=] [NVSEG_LOWER_LIMIT=] @@ -79,7 +79,7 @@ Setting the allocation policy to `even` means resources are always evenly dispat For each query resource allocation request, the HAWQ resource mananger determines the minimum and maximum size of a virtual segment based on multiple factors including query cost, user configuration, table properties, and so on. For example, a hash distributed table requires fixed size of virtual segments. With an even allocation policy, the HAWQ resource manager uses the minimum virtual segment size requirement and evenly dispatches resources to each query resource allocation request in the resource queue.
VSEG\_RESOURCE\_QUOTA='mem:{128mb | 256mb | 512mb | 1024mb | 2048mb | 4096mb | 8192mb | 16384mb | 1gb | 2gb | 4gb | 8gb | 16gb}'
-
Optional. This quota defines how resources are split across multiple virtual segments. For example, when the HAWQ resource manager determines that 256GB memory and 128 vcores should be allocated to the current resource queue, there are multiple solutions on how to divide the resources across virtual segments. For example, you could use a) 2GB/1 vcore \* 128 virtual segments or b) 1GB/0.5 vcore \* 256 virtual segments. Therefore, you can use this attribute to make the HAWQ resource manager calculate the number of virtual segments based on how to divide the memory. For example, if `VSEGMENT_RESOURCE_QUOTA``='mem:512mb'`, then the resource queue will use 512MB/0.25 vcore \* 512 virtual segments. The default value is '`mem:256mb`'. +
Optional. This quota defines how resources are split across multiple virtual segments. For example, when the HAWQ resource manager determines that 256GB memory and 128 vcores should be allocated to the current resource queue, there are multiple solutions on how to divide the resources across virtual segments. For example, you could use a) 2GB/1 vcore \* 128 virtual segments or b) 1GB/0.5 vcore \* 256 virtual segments. Therefore, you can use this attribute to make the HAWQ resource manager calculate the number of virtual segments based on how to divide the memory. For example, if `VSEG_RESOURCE_QUOTA``='mem:512mb'`, then the resource queue will use 512MB/0.25 vcore \* 512 virtual segments. The default value is '`mem:256mb`'. **Note:** To avoid resource fragmentation, make sure that the segment resource capacity configured for HAWQ (in HAWQ Standalone mode: `hawq_rm_memory_limit_perseg`; in YARN mode: `yarn.nodemanager.resource.memory-mb` must be a multiple of the resource quotas for all virtual segments and CPU to memory ratio must be a multiple of the amount configured for `yarn.scheduler.minimum-allocation-mb`.
http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/697fed81/reference/sql/CREATE-RESOURCE-QUEUE.html.md.erb ---------------------------------------------------------------------- diff --git a/reference/sql/CREATE-RESOURCE-QUEUE.html.md.erb b/reference/sql/CREATE-RESOURCE-QUEUE.html.md.erb index 2b16652..8fa6e89 100644 --- a/reference/sql/CREATE-RESOURCE-QUEUE.html.md.erb +++ b/reference/sql/CREATE-RESOURCE-QUEUE.html.md.erb @@ -18,7 +18,7 @@ where \ is:     CORE_LIMIT_CLUSTER=     [ACTIVE_STATEMENTS=] [ALLOCATION_POLICY='even'] - [VSEGMENT_RESOURCE_QUOTA='mem:'] + [VSEG_RESOURCE_QUOTA='mem:'] [RESOURCE_OVERCOMMIT_FACTOR=] [NVSEG_UPPER_LIMIT=] [NVSEG_LOWER_LIMIT=] @@ -77,7 +77,7 @@ Setting the allocation policy to `even` means resources are always evenly dispat For each query resource allocation request, the HAWQ resource manager determines the minimum and maximum size of a virtual segment based on multiple factors including query cost, user configuration, table properties, and so on. For example, a hash distributed table requires fixed size of virtual segments. With an even allocation policy, the HAWQ resource manager uses the minimum virtual segment size requirement and evenly dispatches resources to each query resource allocation request in the resource queue.
VSEG\_RESOURCE\_QUOTA='mem:{128mb | 256mb | 512mb | 1024mb | 2048mb | 4096mb | 8192mb | 16384mb | 1gb | 2gb | 4gb | 8gb | 16gb}'
-
Optional. This quota defines how resources are split across multiple virtual segments. For example, when the HAWQ resource manager determines that 256GB memory and 128 vcores should be allocated to the current resource queue, there are multiple solutions on how to divide the resources across virtual segments. For example, you could use a) 2GB/1 vcore \* 128 virtual segments or b) 1GB/0.5 vcore \* 256 virtual segments. Therefore, you can use this attribute to make the HAWQ resource manager calculate the number of virtual segments based on how to divide the memory. For example, if `VSEGMENT_RESOURCE_QUOTA``='mem:512mb'`, then the resource queue will use 512MB/0.25 vcore \* 512 virtual segments. The default value is '`mem:256mb`'. +
Optional. This quota defines how resources are split across multiple virtual segments. For example, when the HAWQ resource manager determines that 256GB memory and 128 vcores should be allocated to the current resource queue, there are multiple solutions on how to divide the resources across virtual segments. For example, you could use a) 2GB/1 vcore \* 128 virtual segments or b) 1GB/0.5 vcore \* 256 virtual segments. Therefore, you can use this attribute to make the HAWQ resource manager calculate the number of virtual segments based on how to divide the memory. For example, if `VSEG_RESOURCE_QUOTA``='mem:512mb'`, then the resource queue will use 512MB/0.25 vcore \* 512 virtual segments. The default value is '`mem:256mb`'. **Note:** To avoid resource fragmentation, make sure that the segment resource capacity configured for HAWQ (in HAWQ Standalone mode: `hawq_rm_memory_limit_perseg`; in YARN mode: `yarn.nodemanager.resource.memory-mb` must be a multiple of the resource quotas for all virtual segments and CPU to memory ratio must be a multiple of the amount configured for `yarn.scheduler.minimum-allocation-mb`.