[
https://issues.apache.org/jira/browse/NIFI-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15703114#comment-15703114
]
ASF GitHub Bot commented on NIFI-3026:
--------------------------------------
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/1208
I think what @markap14 outlined above would be fine. It would be consistent
with the other changes in this PR. We can certainly address the UX in a
subsequent JIRA however, we cannot go back if we start accepting a comma
separate list in the target URI field of the RPG DTO.
Another option which I'm also fine with would be if we supported specifying
either a single target URI **or** a listing. This would support backward
compatibility while offering support for multiple going forward.
> 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)
