You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hawq.apache.org by "Xiang Sheng (JIRA)" <ji...@apache.org> on 2016/12/22 07:27:58 UTC

[jira] [Assigned] (HAWQ-1231) RM should error out when nvseg in statement level is greater than the guc for nvseg per seg.

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

Xiang Sheng reassigned HAWQ-1231:
---------------------------------

    Assignee: Xiang Sheng  (was: Ed Espino)

> RM should error out when nvseg in statement level is greater than the guc for nvseg per seg.
> --------------------------------------------------------------------------------------------
>
>                 Key: HAWQ-1231
>                 URL: https://issues.apache.org/jira/browse/HAWQ-1231
>             Project: Apache HAWQ
>          Issue Type: Bug
>          Components: Resource Manager
>            Reporter: Xiang Sheng
>            Assignee: Xiang Sheng
>             Fix For: backlog
>
>
> If user set a larget nvseg in statement level, the nvseg is greater than the guc nvseg per seg, rm won't report error. It will allocate according to nvseg per seg. But this cannot satisfy statement level nvseg. RM will timeout at last. This behaviors is not reasonable. We should error out directly and tell user if he wants the nvseg in statement, he must change the guc ( hawq_rm_nvseg_perquery_perseg_limit ) accordingly.



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