[
https://issues.apache.org/jira/browse/NIFI-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15648770#comment-15648770
]
ASF GitHub Bot commented on NIFI-3002:
--------------------------------------
GitHub user mcgilman opened a pull request:
https://github.com/apache/nifi/pull/1189
Remove legacy site to site code to ensure port availability is accurate
NIFI-3002:
- Removing legacy code when retrieving site to site details when the target
instance is this local NiFi.
- Ensures the UI accurately reflects available remote ports.
NIFI-2603:
- Fixing color of remote input/output port status in connection label.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mcgilman/nifi NIFI-3002
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1189.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1189
----
commit 11d54aa8b4a31e81b020740d5d07df4ae23862ef
Author: Matt Gilman <[email protected]>
Date: 2016-11-08T20:57:21Z
NIFI-3002:
- Removing legacy code when retrieving site to site details when the target
instance is this local NiFi.
- Ensures the UI accurately reflects available remote ports.
NIFI-2603:
- Fixing color of remote output port status in connection label.
----
> Remove legacy code for retrieving Site To Site details
> ------------------------------------------------------
>
> Key: NIFI-3002
> URL: https://issues.apache.org/jira/browse/NIFI-3002
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Matt Gilman
> Assignee: Matt Gilman
> Fix For: 1.1.0
>
>
> Earlier versions of Apache NiFi could potentially enter a distributed
> deadlock when load balancing with a Remote Process Group. Retrieval of these
> details was obtained within the framework as a remote call was technically
> unnecessary. Subsequently, these actions were made asynchronous but the port
> retrieval was left in place. This could lead to some confusion as the UI may
> report some ports as available when technically policies may prevent data
> transfers. By removing the legacy code, the UI will accurately reflect the
> port availability.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
