[
https://issues.apache.org/jira/browse/IMPALA-6412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-6412.
-----------------------------------
Fix Version/s: Impala 4.0
Resolution: Fixed
We believe this has been basically fixed with IMPALA-4400 and IMPALA-7984
switching to KRPC and doing some aggregation locally. I will close. There are
optimizations we can make in this part of the code but the memory problems
should be solved (we believe).
> Memory issues with processing of incoming global runtime filters on
> coordinator
> -------------------------------------------------------------------------------
>
> Key: IMPALA-6412
> URL: https://issues.apache.org/jira/browse/IMPALA-6412
> Project: IMPALA
> Issue Type: Bug
> Components: Backend, Distributed Exec
> Affects Versions: Impala 2.11.0
> Reporter: Tim Armstrong
> Priority: Major
> Labels: resource-management, scalability
> Fix For: Impala 4.0
>
>
> This is a tracking JIRA for runtime filter memory issues that occur when
> processing global runtime filters, which is currently done entirely on the
> coordinator. I'll link all related issues that I know about and we can close
> this issue once we're fully satisfied that the problem is resolved.
> Currently the known issues include:
> * All filters are processed on the coordinator, which quickly becomes a
> bottleneck
> * We don't track the memory consumed by thrift strings in incoming RPCs
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
