[jira] [Commented] (HAWQ-1382) Specify necessary setup for hawq_rm_stmt_nvseg and hawq_rm_stmt_vseg_memory
[ https://issues.apache.org/jira/browse/HAWQ-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15929144#comment-15929144 ] ASF GitHub Bot commented on HAWQ-1382: -- Github user janebeckman closed the pull request at: https://github.com/apache/incubator-hawq-docs/pull/103 > Specify necessary setup for hawq_rm_stmt_nvseg and hawq_rm_stmt_vseg_memory > > > Key: HAWQ-1382 > URL: https://issues.apache.org/jira/browse/HAWQ-1382 > Project: Apache HAWQ > Issue Type: Improvement > Components: Documentation >Reporter: Jane Beckman >Assignee: David Yozie > Fix For: 2.2.0.0-incubating > > > You must set hawq_rm_stmt_nvseg before setting hawq_rm_stmt_vseg_memory > To enable statement level, users must set hawq_rm_stmt_nvseg to a number > larger than 0, run desired query, then set it back. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HAWQ-1382) Specify necessary setup for hawq_rm_stmt_nvseg and hawq_rm_stmt_vseg_memory
[ https://issues.apache.org/jira/browse/HAWQ-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925309#comment-15925309 ] ASF GitHub Bot commented on HAWQ-1382: -- Github user dyozie commented on a diff in the pull request: https://github.com/apache/incubator-hawq-docs/pull/103#discussion_r106057640 --- Diff: markdown/bestpractices/managing_resources_bestpractices.html.md.erb --- @@ -110,11 +110,14 @@ ALTER RESOURCE queue1 WITH (VSEG_RESOURCE_QUOTA='mem:2gb'); If there are only occasional queries on Parquet tables with a large page size, use a statement level specification instead of altering the resource queue. For example: ```sql -SET HAWQ_RM_STMT_NVSEG=10; -SET HAWQ_RM_STMT_VSEG_MEMORY='2gb'; -query1; -SET HAWQ_RM_STMT_NVSEG=0; +postgres=# SET hawq_rm_stmt_nvseg=10; +postgres=# SET hawq_rm_stmt_vseg_memory='2gb'; +postgres=# query1; +postgres=# SET hawq_rm_stmt_nvseg=0; +postgres=# SET ``` +***Note:*** To enable the statement level, you must set `hawq_rm_stmt_nvseg` to a value greater than 0 before setting `hawq_rm_stmt_vseg_memory`. After running a query or completing the session, the value of `hawq_rm_stmt_nvseg` should be reset to 0, as shown in the example above. --- End diff -- Change "To enable the statement level" to "To set the parameters at the statement level" > Specify necessary setup for hawq_rm_stmt_nvseg and hawq_rm_stmt_vseg_memory > > > Key: HAWQ-1382 > URL: https://issues.apache.org/jira/browse/HAWQ-1382 > Project: Apache HAWQ > Issue Type: Improvement > Components: Documentation >Reporter: Jane Beckman >Assignee: David Yozie > Fix For: 2.2.0.0-incubating, 2.1.0.0-incubating > > > You must set hawq_rm_stmt_nvseg before setting hawq_rm_stmt_vseg_memory > To enable statement level, users must set hawq_rm_stmt_nvseg to a number > larger than 0, run desired query, then set it back. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HAWQ-1382) Specify necessary setup for hawq_rm_stmt_nvseg and hawq_rm_stmt_vseg_memory
[ https://issues.apache.org/jira/browse/HAWQ-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925306#comment-15925306 ] ASF GitHub Bot commented on HAWQ-1382: -- Github user dyozie commented on a diff in the pull request: https://github.com/apache/incubator-hawq-docs/pull/103#discussion_r106058647 --- Diff: markdown/bestpractices/managing_resources_bestpractices.html.md.erb --- @@ -110,11 +110,14 @@ ALTER RESOURCE queue1 WITH (VSEG_RESOURCE_QUOTA='mem:2gb'); If there are only occasional queries on Parquet tables with a large page size, use a statement level specification instead of altering the resource queue. For example: ```sql -SET HAWQ_RM_STMT_NVSEG=10; -SET HAWQ_RM_STMT_VSEG_MEMORY='2gb'; -query1; -SET HAWQ_RM_STMT_NVSEG=0; +postgres=# SET hawq_rm_stmt_nvseg=10; +postgres=# SET hawq_rm_stmt_vseg_memory='2gb'; +postgres=# query1; +postgres=# SET hawq_rm_stmt_nvseg=0; +postgres=# SET --- End diff -- I'm pretty sure this SET command isn't actually a command to type at the postgres=# prompt, but an output from psqsl. See the example at the end of this PR (each SET command results in psql showing SET). You should make both code blocks similar in this regard. > Specify necessary setup for hawq_rm_stmt_nvseg and hawq_rm_stmt_vseg_memory > > > Key: HAWQ-1382 > URL: https://issues.apache.org/jira/browse/HAWQ-1382 > Project: Apache HAWQ > Issue Type: Improvement > Components: Documentation >Reporter: Jane Beckman >Assignee: David Yozie > Fix For: 2.2.0.0-incubating, 2.1.0.0-incubating > > > You must set hawq_rm_stmt_nvseg before setting hawq_rm_stmt_vseg_memory > To enable statement level, users must set hawq_rm_stmt_nvseg to a number > larger than 0, run desired query, then set it back. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HAWQ-1382) Specify necessary setup for hawq_rm_stmt_nvseg and hawq_rm_stmt_vseg_memory
[ https://issues.apache.org/jira/browse/HAWQ-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925307#comment-15925307 ] ASF GitHub Bot commented on HAWQ-1382: -- Github user dyozie commented on a diff in the pull request: https://github.com/apache/incubator-hawq-docs/pull/103#discussion_r106058017 --- Diff: markdown/resourcemgmt/ConfigureResourceManagement.html.md.erb --- @@ -100,22 +100,25 @@ In some cases, you may want to specify additional resource quotas on the query s The following configuration properties allow a user to control resource quotas without altering corresponding resource queues. -- [hawq\_rm\_stmt\_vseg\_memory](../reference/guc/parameter_definitions.html) - [hawq\_rm\_stmt\_nvseg](../reference/guc/parameter_definitions.html) +- [hawq\_rm\_stmt\_vseg\_memory](../reference/guc/parameter_definitions.html) However, the changed resource quota for the virtual segment cannot exceed the resource queue’s maximum capacity in HAWQ. +***Note:*** The value of `hawq_rm_stmt_vseg_memory` depends on `hawq_rm_stmt_nvseg`, which defines the number of virtual segments used for the query. You must set `hawq_rm_stmt_nvseg` to a value greater than 0 before setting the memory quota for each segment with `hawq_rm_stmt_vseg_memory`. After running a query or completing the session, the value of `hawq_rm_stmt_nvseg` should be reset to 0 to disable the statement level resource quota. --- End diff -- Change "the value of `hawq_rm_stmt_nvseg` should be reset to 0 " to "reset the value of `hawq_rm_stmt_nvseg` to 0" > Specify necessary setup for hawq_rm_stmt_nvseg and hawq_rm_stmt_vseg_memory > > > Key: HAWQ-1382 > URL: https://issues.apache.org/jira/browse/HAWQ-1382 > Project: Apache HAWQ > Issue Type: Improvement > Components: Documentation >Reporter: Jane Beckman >Assignee: David Yozie > Fix For: 2.2.0.0-incubating, 2.1.0.0-incubating > > > You must set hawq_rm_stmt_nvseg before setting hawq_rm_stmt_vseg_memory > To enable statement level, users must set hawq_rm_stmt_nvseg to a number > larger than 0, run desired query, then set it back. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HAWQ-1382) Specify necessary setup for hawq_rm_stmt_nvseg and hawq_rm_stmt_vseg_memory
[ https://issues.apache.org/jira/browse/HAWQ-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925308#comment-15925308 ] ASF GitHub Bot commented on HAWQ-1382: -- Github user dyozie commented on a diff in the pull request: https://github.com/apache/incubator-hawq-docs/pull/103#discussion_r106058705 --- Diff: markdown/resourcemgmt/ConfigureResourceManagement.html.md.erb --- @@ -100,22 +100,25 @@ In some cases, you may want to specify additional resource quotas on the query s The following configuration properties allow a user to control resource quotas without altering corresponding resource queues. -- [hawq\_rm\_stmt\_vseg\_memory](../reference/guc/parameter_definitions.html) - [hawq\_rm\_stmt\_nvseg](../reference/guc/parameter_definitions.html) +- [hawq\_rm\_stmt\_vseg\_memory](../reference/guc/parameter_definitions.html) However, the changed resource quota for the virtual segment cannot exceed the resource queue’s maximum capacity in HAWQ. +***Note:*** The value of `hawq_rm_stmt_vseg_memory` depends on `hawq_rm_stmt_nvseg`, which defines the number of virtual segments used for the query. You must set `hawq_rm_stmt_nvseg` to a value greater than 0 before setting the memory quota for each segment with `hawq_rm_stmt_vseg_memory`. After running a query or completing the session, the value of `hawq_rm_stmt_nvseg` should be reset to 0 to disable the statement level resource quota. + In the following example, when executing the next query statement, the HAWQ resource manager will attempt to allocate 10 virtual segments and each segment has a 256MB memory quota. + ``` sql +postgres=# SET hawq_rm_stmt_nvseg=10; +SET postgres=# SET hawq_rm_stmt_vseg_memory='256mb'; SET -postgres=# SET hawq_rm_stmt_nvseg=10; +postgres=# SELECT FROM WHERE --- End diff -- Should at least terminate this example with a semicolon; > Specify necessary setup for hawq_rm_stmt_nvseg and hawq_rm_stmt_vseg_memory > > > Key: HAWQ-1382 > URL: https://issues.apache.org/jira/browse/HAWQ-1382 > Project: Apache HAWQ > Issue Type: Improvement > Components: Documentation >Reporter: Jane Beckman >Assignee: David Yozie > Fix For: 2.2.0.0-incubating, 2.1.0.0-incubating > > > You must set hawq_rm_stmt_nvseg before setting hawq_rm_stmt_vseg_memory > To enable statement level, users must set hawq_rm_stmt_nvseg to a number > larger than 0, run desired query, then set it back. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
