[
https://issues.apache.org/jira/browse/NIFI-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15703084#comment-15703084
]
ASF GitHub Bot commented on NIFI-3026:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/1208
@ijokarumawak thanks for the update. The new commit perfectly addresses the
concern that I had with the Builder. I do think we should update the
RemoteProcessGroup & DTO as well. The DTO could still have a getTargetUri()
that would return the first value entered, just as the builder does now, and
then also have a getTargetUris() that returns all of them. Along those lines,
it may make sense to not event deprecated the getUri() method and simply
document that it returns the first one entered by the user and the getUris()
method returns all of them. The DTO may also require having a setTargetUri()
and setTargetUris(). I'm just very hesitant to return a comma-separated list of
URI's when we have a method named getUri(), etc. This would also have the added
benefit of keeping the UI clean, showing a single URI if we want to. @mcgilman
do you have any thoughts on how the RPG DTO should change (or not)?
> 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)
