You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2018/06/08 00:31:00 UTC
[jira] [Commented] (IMPALA-7145) Memory leak when looping
test_spilling_naaj
[ https://issues.apache.org/jira/browse/IMPALA-7145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16505543#comment-16505543 ]
Tim Armstrong commented on IMPALA-7145:
---------------------------------------
I'm pretty sure that we're missing a EVP_CIPHER_CTX_cleanup() call. Testing the fix by looping it overnight.
> Memory leak when looping test_spilling_naaj
> -------------------------------------------
>
> Key: IMPALA-7145
> URL: https://issues.apache.org/jira/browse/IMPALA-7145
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 2.13.0, Impala 3.1.0
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Blocker
> Labels: resource-management
>
> I tried looping this test for a while to flush out a different issue and discovered a memory leak:
> {noformat}
> while impala-py.test tests/query_test/test_spilling.py -k naaj -n4 --verbose; do date; done
> {noformat}
> Eventually the test fails with "Memory Limit Exceeded" and there is a huge amount of untracked memory reported on /memz.
> I tried running the heap growth profiler and the only suspicious thing I saw was CRYPTO_malloc, similar to IMPALA-6792. My current hypothesis is that it's something related to disk spill encryption and we haven't noticed it before because we had disk spill encryption off.
> If I disable encryption "start-impala-cluster.py --impalad_args=--disk_spill_encryption=false" then I don't see the leak.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org