[
https://issues.apache.org/jira/browse/NIFI-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405906#comment-15405906
]
ASF GitHub Bot commented on NIFI-2035:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/690
@YolandaMDavis after reviewing the NPE I changed my mind - you do appear to
be causing the issue manually :) The NPE was another place where we needed to
verify that the source and destination existed. However, you will sometimes see
that it creates the connection successfully, which is why I didn't think your
method would work to test. The RPG refreshes the ports in the background, so
depending on when you try to create the connection, it may or may not believe
the port exists. Of course, a NullPointer is always wrong, though. Will update
PR to address that.
> 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)
