[
https://issues.apache.org/jira/browse/HAWQ-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008288#comment-15008288
]
ASF GitHub Bot commented on HAWQ-170:
-------------------------------------
GitHub user huor opened a pull request:
https://github.com/apache/incubator-hawq/pull/119
HAWQ-170. Rename GUC gp_vmem_protect_limit to hawq_re_memory_overcommit_max
to reflect latest memory enforcement implementation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/huor/incubator-hawq github_huor_re
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-hawq/pull/119.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #119
----
commit e5d7189be5195c3c9adc9ec3e2ef8c1e4399e7d3
Author: Ruilong Huo <[email protected]>
Date: 2015-11-17T08:42:57Z
HAWQ-170. Rename GUC gp_vmem_protect_limit to hawq_re_memory_overcommit_max
to reflect latest memory enforcement implementation
----
> 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 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
