[
https://issues.apache.org/jira/browse/NIFI-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407631#comment-15407631
]
ASF GitHub Bot commented on NIFI-2035:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/690
Hey @YolandaMDavis - the changes that were made in the later commit will
not completely prevent the IllegalArgumentException from being thrown in
verifyCreate... it's still possible because after the authorization is
performed, it's still possible for the background thread to change the ports.
But you'd have to have *REALLY* good timing to hit that :) Very unlikely you'd
be able to trigger it intentionally. So if you think the change looks
reasonable and I didn't break anything, I think it should be good to go
> 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)
