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

Posted to issues@kudu.apache.org by "Thomas Tauber-Marshall (JIRA)" <ji...@apache.org> on 2018/07/06 20:34:00 UTC

[jira] [Closed] (KUDU-2493) Aggregator mem usage isn't reflected in summary

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

Thomas Tauber-Marshall closed KUDU-2493.
----------------------------------------
    Resolution: Invalid

meant to file against Impala

> Aggregator mem usage isn't reflected in summary
> -----------------------------------------------
>
>                 Key: KUDU-2493
>                 URL: https://issues.apache.org/jira/browse/KUDU-2493
>             Project: Kudu
>          Issue Type: Bug
>            Reporter: Thomas Tauber-Marshall
>            Priority: Critical
>
> Since IMPALA-110 (part 2) went  in, which refactored 'PartitionedAggregationNode' and introduces 'Aggregator', the memory used by Aggregator is not reflected in the exec summary, where it should be listed under the corresponding AggregationNode/StreamingAggregationNode, as Aggregator's MemTracker is initialized with the RuntimeState::instance_mem_tracker as its parent, rather than ExecNode::mem_tracker



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)