[ 
https://issues.apache.org/jira/browse/NIFI-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437517#comment-15437517
 ] 

ASF GitHub Bot commented on NIFI-2669:
--------------------------------------

GitHub user markap14 opened a pull request:

    https://github.com/apache/nifi/pull/949

    NIFI-2669: Ensure that if Exception is thrown during Transaction init…

    …ialization that the underlying client is closed/cleaned up. Also ensure 
that we generate bulletins when logging error/warn level log messages

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/markap14/nifi NIFI-2669

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/949.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #949
    
----
commit 8a079a1b889b79d6dcd0546f5e8673fe13cd7eb0
Author: Mark Payne <[email protected]>
Date:   2016-08-25T17:25:24Z

    NIFI-2669: Ensure that if Exception is thrown during Transaction 
initialization that the underlying client is closed/cleaned up. Also ensure 
that we generate bulletins when logging error/warn level log messages

----


> HTTP-based Site-to-Site leaks threads/memory when unable to communicate with 
> remote instance
> --------------------------------------------------------------------------------------------
>
>                 Key: NIFI-2669
>                 URL: https://issues.apache.org/jira/browse/NIFI-2669
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Blocker
>             Fix For: 1.0.0
>
>
> I am using HTTP-based site-to-site to communicate with a remote instance of 
> NiFi. I am seeing problems communicating, which is okay. But I am seeing CPU 
> load of 600-700 on my system with 32 cores. I am also seeing in a thread dump 
> 10's to 100's threads with the name "I/O dispatcher" and am seeing OOME's. A 
> heap dump shows that the OOME is caused by 64K byte arrays, each being filled 
> with 0's. The byte[] is coming from class 
> org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to