[ 
https://issues.apache.org/jira/browse/NIFI-5841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Advith Nagappa updated NIFI-5841:
---------------------------------
    Summary: PutHive3Streaming processor Mem Leak  (was: PutHive3Streaming 
processor )

> PutHive3Streaming processor Mem Leak
> ------------------------------------
>
>                 Key: NIFI-5841
>                 URL: https://issues.apache.org/jira/browse/NIFI-5841
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.8.0, 1.7.1
>         Environment: Hive 3.1.*
>            Reporter: Advith Nagappa
>            Priority: Major
>
> Nifi versions: 1,7.1 and 1.8.0
> nifi/nifi-nar-bundles/nifi-hive-bundle/nifi-hive3-processors/src/main/java/org/apache/nifi/processors/hive/PutHive3Streaming.java**
> , line 417 seems redundant,
> {code:java}
> ShutdownHookManager.addShutdownHook(hiveStreamingConnection::close, 
> FileSystem.SHUTDOWN_HOOK_PRIORITY + 1){code}
>  
> Whereas, Hive 3.0.0 did not addShutDownHook within connect() method, Hive 
> 3.1.* does:
>  
> hive/streaming/src/java/org/apache/hive/streaming/HiveStreamingConnection.java
>  
> {code:java}
> ShutdownHookManager.addShutdownHook(streamingConnection::close, 
> FileSystem.SHUTDOWN_HOOK_PRIORITY + 1);{code}
> This creates two references to the shutdownhook object per transaction out of 
> which only one is ever removed and slow/fast degradation of heap space 
> depending on the velocity of transactions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to