[
https://issues.apache.org/jira/browse/NIFI-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15673773#comment-15673773
]
ASF GitHub Bot commented on NIFI-3026:
--------------------------------------
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1208#discussion_r88453728
--- Diff:
nifi-commons/nifi-site-to-site-client/src/main/java/org/apache/nifi/remote/client/SiteToSiteClient.java
---
@@ -560,7 +560,8 @@ public SiteToSiteClient build() {
}
/**
- * @return the configured URL for the remote NiFi instance
+ * @return the configured URL for the remote NiFi instance.
+ * The URL string possibly contains multiple URL entries in
comma-separated format.
*/
public String getUrl() {
--- End diff --
@ijokarumawak my concern is not code within the NiFi codebase, but rather
code written by third parties. I believe there are others already who have code
unrelated to NiFi, that actually depend on this client lib for
sending/receiving data.
> 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)
