[
https://issues.apache.org/jira/browse/IMPALA-7256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Tauber-Marshall resolved IMPALA-7256.
--------------------------------------------
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> Aggregator mem usage isn't reflected in summary
> -----------------------------------------------
>
> Key: IMPALA-7256
> URL: https://issues.apache.org/jira/browse/IMPALA-7256
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 3.1.0
> Reporter: Thomas Tauber-Marshall
> Assignee: Thomas Tauber-Marshall
> Priority: Blocker
> Labels: observability, supportability
> Fix For: Impala 3.1.0
>
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
