[
https://issues.apache.org/jira/browse/NIFI-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405943#comment-15405943
]
ASF GitHub Bot commented on NIFI-2035:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/690
@YolandaMDavis I updated the PR with a new commit so that you can see what
changed. It looks like the way to cause it to hit is to drag a connection from
a Processor to the Remote Process Group, and then once the dialog is up to
choose which port, remove the port from a different browser tab, and then wait
30 seconds for the RPG to refresh ports. Then click the "Apply" button on the
"Add Connection" dialog
> 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)
