You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Ruilong Huo (JIRA)" <ji...@apache.org> on 2015/11/17 09:48:10 UTC
[jira] [Updated] (HAWQ-170) Rename GUC gp_vmem_protect_limit to
hawq_re_memory_overcommit_max to reflect latest memory enforcement
implementation
[ https://issues.apache.org/jira/browse/HAWQ-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruilong Huo updated HAWQ-170:
-----------------------------
Description: GUC gp_vmem_protect_limit was used as vmem memory quota per HAWQ segment. Now, we implemented resource enforcement but leveraging gp_vmem_protect_limit as the GUC for maximum overcommit of memory quota per HAWQ physical segment. It should be renamed to hawq_re_memory_overcommit_max to reflect that. (was: GUC gp_vmem_protect_limit was used as vmem memory quota for HAWQ segment in 1.x. In HAWQ 2.0, we implemented resource enforcement but leveraging gp_vmem_protect_limit as the GUC for maximum overcommit of memory quota per HAWQ physical segment. It should be renamed to hawq_re_memory_overcommit_max to reflect that.)
> Rename GUC gp_vmem_protect_limit to hawq_re_memory_overcommit_max to reflect latest memory enforcement implementation
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: HAWQ-170
> URL: https://issues.apache.org/jira/browse/HAWQ-170
> Project: Apache HAWQ
> Issue Type: Improvement
> Components: Resource Manager
> Reporter: Ruilong Huo
> Assignee: Ruilong Huo
>
> GUC gp_vmem_protect_limit was used as vmem memory quota per HAWQ segment. Now, we implemented resource enforcement but leveraging gp_vmem_protect_limit as the GUC for maximum overcommit of memory quota per HAWQ physical segment. It should be renamed to hawq_re_memory_overcommit_max to reflect that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)