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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3026:
--------------------------------------

Github user ijokarumawak commented on the issue:

    https://github.com/apache/nifi/pull/1208
  
    Hi @markap14 @mcgilman 
    
    I've updated the PR commit with the latest master.
    Explicitly separated the URI and URIs. 
    
    I've also updated these RPG UI components to use the plural URLs.
    These display Name and URIs. It looked too verbose if URLs are used for 
both Name and URIs, so I used URI for the Name if Name is not specified:
    
    <img width="1115" alt="3026-ui-rpg" 
src="https://cloud.githubusercontent.com/assets/1107620/20754872/3bfd7b88-b750-11e6-872f-b3ae814eeff3.png";>
    
    
    Tried to update all UI components that I was aware of, but I didn't want to 
make this PR huge and rush to change following components, so that we can 
discuss more about the details with separated JIRAs.
    
    ## Known UI components those are not updated to use URLs
    
    ### Search component
    
    RPGs can be searched by target URI. I haven't updated search related 
components to use plural URIs. So only the first URI is searchable, and shown 
in the UI right now.
    
    <img width="487" alt="3026-ui-search" 
src="https://cloud.githubusercontent.com/assets/1107620/20755069/fab5d430-b750-11e6-93cf-2d6957b537e2.png";>
    
    ### Component Status and Summary
    
    <img width="1008" alt="3026-ui-status" 
src="https://cloud.githubusercontent.com/assets/1107620/20755188/6508fc68-b751-11e6-9ac4-79b55dd660b1.png";>
    
    ### Action History
    
    When RPG is updated, audit event is stored. I think we should use URIs 
here. But in order to do so, we have to alter the REMOTE_PROCESS_GROUP_DETAILS 
table in database repository. I don't know what would be a proper migration 
process at this point, so didn't touch it within this PR.
    
    <img width="1036" alt="3026-ui-action-history" 
src="https://cloud.githubusercontent.com/assets/1107620/20755303/c9db3084-b751-11e6-8a94-0b40e2e8e580.png";>
    
    Hope this PR would be sufficient to provide the core support of multiple 
URIs for better connectivity with NiFi cluster via Site-to-Site. Thanks for 
reviewing!


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