[
https://issues.apache.org/jira/browse/NIFI-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405891#comment-15405891
]
ASF GitHub Bot commented on NIFI-2035:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/690
@YolandaMDavis I will look into the NPE. The test case that you described
will not cause the issue that you are expecting, though. There is no way to
test it without doing some funky stuff with breakpoints, etc. It is a timing
issue. Would recommend that a code review and testing that the change doesn't
break anything is sufficient.
> 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)
