You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (JIRA)" <ji...@apache.org> on 2016/11/11 08:17:58 UTC

[jira] [Commented] (NIFI-3026) S2S initial connection behavior enhancement

    [ https://issues.apache.org/jira/browse/NIFI-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15656478#comment-15656478 ] 

Pierre Villard commented on NIFI-3026:
--------------------------------------

+1 thanks Koji, it'll be very useful!

> 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)