You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Amy (JIRA)" <ji...@apache.org> on 2017/02/16 02:13:41 UTC
[jira] [Closed] (HAWQ-1315) Function validateResourcePoolStatus()
in resourcepool.c is logging the wrong information
[ https://issues.apache.org/jira/browse/HAWQ-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amy closed HAWQ-1315.
---------------------
Resolution: Fixed
> Function validateResourcePoolStatus() in resourcepool.c is logging the wrong information
> ----------------------------------------------------------------------------------------
>
> Key: HAWQ-1315
> URL: https://issues.apache.org/jira/browse/HAWQ-1315
> Project: Apache HAWQ
> Issue Type: Bug
> Components: Resource Manager
> Reporter: Xiang Sheng
> Assignee: Amy
> Fix For: 2.3.0.0-incubating
>
>
> The function "validateResourcePoolStatus()" in "resourcepool.c" is not logging the correct information in the message printed by "elog()" function in line 4123. In the snippet below:
> {code}
> if ( totalallocmem > mem || totalalloccore > core )
> {
> elog(WARNING, "HAWQ RM Validation. Allocated too much resource in resource "
> "pool (%d MB, %lf CORE), maximum capacity (%d MB, %d CORE)",
> totalallocmem,
> totalalloccore,
> core,
> mem);
> }
> {code}
> The third and fourth parameters ('core' and 'mem') are swapped; the third string placeholder should be the maximum memory capacity, but it is printing the cores. The same happens with the fourth string placeholder.
> This leads to log messages of this kind in hawq master log:
> {code}
> 2017-02-02 01:30:03.014708 CET,,,p351048,th-384374496,,,,0,con4,,seg-10000,,,,,"WARNING","01000","HAWQ RM Validation. Allocated too much resource in resource pool (49152 MB, 6.000000 CORE), maximum capacity (5 MB, 40960 CORE)",,,,,,,0,,"resourcepool.c",4123,
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)