[
https://issues.apache.org/jira/browse/NIFI-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15403324#comment-15403324
]
ASF GitHub Bot commented on NIFI-2035:
--------------------------------------
Github user YolandaMDavis commented on the issue:
https://github.com/apache/nifi/pull/690
@markap14 during testing I am seeing unexpected behaviors/errors and wanted
to validate my test case. My configuration is as follows:
- 1 standalone nifi server with a Processor Group and an output port
- A 2 node cluster with a Processor Group containing an input port and a
Remote Processor Group that points to the standalone server
The goal of the test was to ensure that if an attempt is made to create a
new connection from the Remote Processor Group to the Processor Group on the
cluster, and the output port on the standalone (remote pg) is removed just
before the add, then the system will display/log IllegalArgumentException
(specifically related to the source not found).
During my tests the behavior has been mostly the following:
1) A NullPointerException occurs just before the verifyCreate method in
StandardConnectionDAO is called
2) If the port is removed a few seconds before creating a connection then
the connection is created successfully with no logged errors.
Both errors prevented me from testing that IllegalArgumentExceptions would
be thrown in this case (since the nullpointer exception happened
Attached are snapshots of the nifi-user.log with the nullpointer exception
that occurred on several of the runs.
Is this test a feasible one and appropriate for this case? If so I would
recommend resolution of this issue before restesting.
[node2-nifi-user-snapshot.log.txt](https://github.com/apache/nifi/files/395231/node2-nifi-user-snapshot.log.txt)
<img width="1440" alt="unexpectedconnectionsuccess"
src="https://cloud.githubusercontent.com/assets/1371858/17317043/8df4bc98-5847-11e6-8d1e-39fc4703bd29.png";>
Also have video of errors if needed
> 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)
![https://cloud.githubusercontent.com/assets/1371858/17317043/8df4bc98-5847-11e6-8d1e-39fc4703bd29.png"](https://cloud.githubusercontent.com/assets/1371858/17317043/8df4bc98-5847-11e6-8d1e-39fc4703bd29.png"){kind=link}