You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/07/20 17:14:20 UTC

[jira] [Commented] (NIFI-2035) Connection creation needs to verify that source and destination both exist during 1st phase of 2 phase commit

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

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

GitHub user markap14 opened a pull request:

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

    NIFI-2035: Verify existence of source and destination when creating a…

    … connection

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

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

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

    https://github.com/apache/nifi/pull/690.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 #690
    
----
commit 07cc1748864a69ded3a62e6cb0debe22e4183586
Author: Mark Payne <ma...@hotmail.com>
Date:   2016-06-20T18:55:08Z

    NIFI-2035: Verify existence of source and destination when creating a connection

----


> Connection creation needs to verify that source and destination both exist during 1st phase of 2 phase commit
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-2035
>                 URL: https://issues.apache.org/jira/browse/NIFI-2035
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>             Fix For: 1.0.0
>
>
> When a connection is created, we don't verify in the first step that both the source and destination exist. In the case of a Remote Process Group, where the ports change in the background, this can become problematic, we one node in the cluster may not have the same ports as another and the connection creation could end up failing on that node, resulting in the node getting kicked out of the cluster. We should also verify that the new destination exists when updating a connection if its destination changes, as this could happen there as well.



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