You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Lei Chang (JIRA)" <ji...@apache.org> on 2015/11/21 03:59:11 UTC

[jira] [Reopened] (HAWQ-47) Make user able to set statement level resource usage.

     [ https://issues.apache.org/jira/browse/HAWQ-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lei Chang reopened HAWQ-47:
---------------------------

> Make user able to set statement level resource usage.
> -----------------------------------------------------
>
>                 Key: HAWQ-47
>                 URL: https://issues.apache.org/jira/browse/HAWQ-47
>             Project: Apache HAWQ
>          Issue Type: New Feature
>          Components: Resource Manager
>            Reporter: Yi Jin
>            Assignee: Yi Jin
>             Fix For: 2.0.0-beta-incubating
>
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> SET STATEMENT_VSEG_MEM=memory_units
> SET STATEMENT_NVSEG=<integer>
> memory_units ::= 128mb|256mb|512mb|1024mb|1gb|2gb|4gb|8gb|16gb 
> Resource manager will try to reserve expected resource for current statement execution. The default value of STATEMENT_NVSEG is 0, which means the statement level setting is not activated, when STATEMENT_NVSEG is greater than zero, STATEMENT_MEM overrides the resource queue virtual segment resource quota. Memory core ratio derived by resource queue hierarchy and cluster capacity. 
> If the expected resource specified by STATEMENT_MEM and STATEMENT_NVSEG can not be satisfied due to various reason, the session is timed out.
> Yi Jin <yj...@pivotal.io>
> Oct 8 (5 days ago)
> to Lei, Jiali, Amy 
> 1) If the expected resource specified by STATEMENT_MEM and STATEMENT_NVSEG can not be satisfied due to queue capacity limits, the error is reported at once, the session is aborted; 
> 2) The setting of statement level resource may cause different query plan generated; (Change code for passing this into optimizer??)
> 3) If the expected resource can not be satisfied by the other various reasons, the session is timed out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)