impala-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Armstrong <tarmstr...@cloudera.com>
Subject Re: Impala Memory Leak (version 2.7.0-cdh5.10.2 )
Date Fri, 29 Sep 2017 18:30:31 GMT
It's not a memory leak, it's a query lifecycle issue. You have fragments
from two queries 2741ad08c43062bc:608bdb9500000000 and
8041bf903a5c7916:2eba50b100000000 that haven't been torn down. There are
various ways that this could happen but I don't know based on the
information provided.

I would check if those queries are still running and if you can cancel them
via Cloudera Manager or the Impala daemon web UI on the coordinator.

On Fri, Sep 29, 2017 at 1:11 AM, Dong Bo 董博 <dongbo@fosun.com> wrote:

> Hi Experts,
>
>
>
> We are running queries on impalad version 2.7.0-cdh5.10.2 RELEASE (build 38c989c0330ea952133111e41965ff9af96412d3),
and issued with a memory leak problem on the impala deamon .
>
> Once query end with error Memory limit exceeded , the allocated memory
> won’t be free until impala deamon restarted.   Memory limit exceeded is in
> attachement.
>
>
>
> I find jira tickets https://issues.apache.org/jira/browse/IMPALA-3589 ,
> https://issues.apache.org/jira/browse/IMPALA-3582 with same issue as I am
> facing tagged as “Fixed” in version 2.6.0, but strange I am still facing
> the issue in a higher version.
>
>
>
> Please kindly advise , it will be very helpful.
>
>
>
> Thanks & Regards
>
> Carl Dong
>
>
>
>
>
>
>

Mime
View raw message