hawq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From yo...@apache.org
Subject [39/50] [abbrv] incubator-hawq-docs git commit: VSEGMENT_RESOURCE_QUOTA to VSEG_RESOURCE_QUOTA
Date Thu, 29 Sep 2016 17:22:53 GMT
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 <lowen@pivotal.io>
Authored: Tue Sep 27 08:42:46 2016 -0700
Committer: Lisa Owen <lowen@pivotal.io>
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 \<queue\_attribute\> is:
    [CORE_LIMIT_CLUSTER=<percentage>]
    [ACTIVE_STATEMENTS=<integer>]
    [ALLOCATION_POLICY='even']
-   [VSEGMENT_RESOURCE_QUOTA='mem:<memory_units>']
+   [VSEG_RESOURCE_QUOTA='mem:<memory_units>']
    [RESOURCE_OVERCOMMIT_FACTOR=<double>]
    [NVSEG_UPPER_LIMIT=<integer>]
    [NVSEG_LOWER_LIMIT=<integer>]
@@ -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.</dd>
 
 <dt>VSEG\_RESOURCE\_QUOTA='mem:{128mb | 256mb | 512mb | 1024mb | 2048mb | 4096mb |
8192mb | 16384mb | 1gb | 2gb | 4gb | 8gb | 16gb}'</dt>
-<dd>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`'.
+<dd>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`.</dd>
 

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 \<queue\_attribute\> is:
     CORE_LIMIT_CLUSTER=<percentage>
     [ACTIVE_STATEMENTS=<integer>]
     [ALLOCATION_POLICY='even']
-    [VSEGMENT_RESOURCE_QUOTA='mem:<memory_units>']
+    [VSEG_RESOURCE_QUOTA='mem:<memory_units>']
     [RESOURCE_OVERCOMMIT_FACTOR=<double>]
     [NVSEG_UPPER_LIMIT=<integer>]
     [NVSEG_LOWER_LIMIT=<integer>]
@@ -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.</dd>
 
 <dt>VSEG\_RESOURCE\_QUOTA='mem:{128mb | 256mb | 512mb | 1024mb | 2048mb | 4096mb |
8192mb | 16384mb | 1gb | 2gb | 4gb | 8gb | 16gb}' </dt>
-<dd>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`'.
+<dd>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`.</dd>
 


Mime
View raw message