[
https://issues.apache.org/jira/browse/NIFI-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15435746#comment-15435746
]
ASF subversion and git services commented on NIFI-2459:
-------------------------------------------------------
Commit a3586e04d9978e105cc5645e893dc6d77b79b86e in nifi's branch
refs/heads/master from [~ijokarumawak]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=a3586e0 ]
NIFI-2459: Site-to-Site bootstrap node failure
Refresh remote peer statuses even if the bootstrap node goes down.
Migrate existing code which handles the situation from
EndpointConnectionPool to PeerSelector, so that both RAW and HTTP
transport protocol has the same capability.
This closes #927.
> HTTP Site-to-Site can't update remote peer topology if the "bootstrap url"
> node is down
> ---------------------------------------------------------------------------------------
>
> Key: NIFI-2459
> URL: https://issues.apache.org/jira/browse/NIFI-2459
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.0.0
> Reporter: Koji Kawamura
> Fix For: 1.0.0
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> To establish a Site-to-Site protocol, a client NiFi uses the remote NiFi API
> url that is specified as 'URL' at the creation of a Remote Process Group
> (let's call it as 'bootstrap url').
> Currently, HTTP Site-to-Site keeps using the same 'bootstrap url', even if
> the remote node goes down. If the bootstrap node went down, Site-to-Site data
> transfer will keep working, but it can't update remote peer topology.
> RAW socket version cares about this scenario by asking updated peer
> information with every nodes that it has connected before, until it gets a
> successful response.
> HTTP version should follow how RAW version handles this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
