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

ASF subversion and git services commented on NIFI-3026:
-------------------------------------------------------

Commit 7c5bd876bdd49ec14482a24dd31a073757f06ed4 in nifi's branch 
refs/heads/master from [~ijokarumawak]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=7c5bd87 ]

NIFI-3026: Support multiple remote target URLs

- Added urls in addition to the existing url, to support multiple target
  URLs
- Backward compatibility is provided by returning the first url if
  multipe urls are specified, but component accessing the url doesn't
support multiple urls
- UI is not fully updated yet. Following UI components are planned to be updated
  by different commits
  - Search component: only the first URL is searchable and shown
  - Component status: RPG status shows only the first URL
  - Component action history: only the first URL is searchable and shown
  - Updated Search component to use URLs.

This closes #1208.


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

Reply via email to