You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Gideon Korir (JIRA)" <ji...@apache.org> on 2019/01/10 14:00:00 UTC
[jira] [Resolved] (NIFI-5946) Hive3Streaming memory leak
[ https://issues.apache.org/jira/browse/NIFI-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gideon Korir resolved NIFI-5946.
--------------------------------
Resolution: Duplicate
Fix Version/s: 1.9.0
> Hive3Streaming memory leak
> --------------------------
>
> Key: NIFI-5946
> URL: https://issues.apache.org/jira/browse/NIFI-5946
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.8.0
> Environment: Rhel 7.5
> Open jdk 1.8
> NiFi 1.8
> HDP 3
> Reporter: Gideon Korir
> Priority: Major
> Fix For: 1.9.0
>
> Attachments: nifi_memory_leak.png
>
>
> Our NiFi instance has been leaking memory since started using Hive3Streaming processor and now we are seeing memory usage of 60+ GB. Looking at the processor code it seems like we are:
> # Creating a new StreamingConnection with each flow file
> # Registering a shutdown hook via <code>ShutdownHookManager.addShutdownHook</code> that should close the connection
> # Closing the connection and not removing the shutdown hook.
> The Runnable captures the connection and conf objects, and since our NiFi instance has been running continuously and the JVM hasn't shutdown (3 weeks +) the ShutdownHookManager is still holding reference to the connections created since causing the memory leak.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)