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

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

GitHub user markap14 opened a pull request:

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

    NIFI-2651: Ensure that when we disable transmission on an RPG that we…

    … interrupt any transactions in progress for http-based site-to-site

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

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

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

    https://github.com/apache/nifi/pull/937.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 #937
    
----
commit 8f103d7c6e37c4ed1b4726ecd867a89aa9c29405
Author: Mark Payne <[email protected]>
Date:   2016-08-25T01:06:30Z

    NIFI-2651: Ensure that when we disable transmission on an RPG that we 
interrupt any transactions in progress for http-based site-to-site

----


> Remote Process Group does not stop immediately when using HTTP-based 
> Site-to-Site
> ---------------------------------------------------------------------------------
>
>                 Key: NIFI-2651
>                 URL: https://issues.apache.org/jira/browse/NIFI-2651
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Critical
>             Fix For: 1.0.0
>
>         Attachments: HTTP_Site-to-Site_with_Large_Data_Chunks.xml
>
>
> If we stop a Remote Process Group that is using the RAW Site-to-Site 
> protocol, it stops immediately, interrupting any transaction that is in 
> progress. If we stop a Remote Process Group that is using HTTP Site-to-Site 
> Protocol, though, the RPG waits until the current transactions have finished.



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

Reply via email to