[
https://issues.apache.org/jira/browse/NIFI-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15678709#comment-15678709
]
ASF GitHub Bot commented on NIFI-3026:
--------------------------------------
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/1208
@markap14 I'm still not 100% sure if it addresses your concern.. but I've
updated the code.
RemoteProcessGroup has `getTargetUri` method that returns a String. I
wondered if we should do the same thing with this, by adding `getTargetUris`,
but I left it as it is. Because if we do, we may want to change
RemoteProcessGroupDTO as well, it will change NiFi Web REST API data format..
Local contrib check has passed, and now I'm testing it with running NiFi
environments. It will take a while to go through a variety of S2S tests. But I
think it's ready for code review.
Would you take a look and give me feedback?
> S2S initial connection behavior enhancement
> -------------------------------------------
>
> Key: NIFI-3026
> URL: https://issues.apache.org/jira/browse/NIFI-3026
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework, Core UI
> Reporter: Koji Kawamura
> Assignee: Koji Kawamura
>
> s2s client behavior and initial connection improvement is needed.
> Current experience is this: I, as a client (e.g. minifi), connect to a nifi
> cluster of e.g. 10 nodes. but i need to specify 1 node URL to establish this
> connection. this node may not be available 100% and go down, in which case my
> initial connection won't work.
> Once S2S makes the first connection, it then has a list of all nodes, and can
> check their status. But first connection failure would be a concern if the
> specified URL is somehow not working. Usually for these problems, the client
> should be able to specify multiple urls (according to multiple target cluster
> nodes), comma-separated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
