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

[jira] [Commented] (NIFI-2082) When a node is disconnected from cluster, it should be made extremely obvious in the UI

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

Rob Moran commented on NIFI-2082:
---------------------------------

Following up on my original comment, I propose the following. Reference the attached mockups.

When a user opens the UI on a node that is disconnected from the cluster:
* Immediately display a warning dialog – see *nifi-2082_disconnected-node-dialog*. The dialog should be displayed each time a user loads the UI, refreshes via their browser Refresh button, etc. 
* Apply a unique style to the cluster icon in the flow status bar – see *nifi-2082_cluster-warning*
* When a user hovers over the cluster icon, display a tooltip repeating the warning dialog message:
bq. This node is not currently connected to the cluster
bq. Any modification to the data flow made here will not replicate across the cluster

When a user accesses the UI of the other _connected_ nodes:
* Apply the same unique style to the cluster icon in the flow status bar – see *nifi-2082_cluster-warning*
* When the user hovers over the cluster icon, display a tooltip:
(For one disconnected node)
bq. The following node is not currently connected to the cluster: <node-address>
bq. Any modification to the data flow made here will be reflected on this node when it reconnects
(For multiple disconnected nodes)
bq. The following nodes are not currently connected to the cluster: <node-address-1>; <node-address-2>
bq. Any modification to the data flow made here will be reflected on these nodes when they reconnect

> When a node is disconnected from cluster, it should be made extremely obvious in the UI
> ---------------------------------------------------------------------------------------
>
>                 Key: NIFI-2082
>                 URL: https://issues.apache.org/jira/browse/NIFI-2082
>             Project: Apache NiFi
>          Issue Type: Sub-task
>          Components: Core UI
>    Affects Versions: 1.0.0
>            Reporter: Mark Payne
>            Priority: Critical
>             Fix For: 1.0.0
>
>         Attachments: nifi-2082_cluster-warning.png, nifi-2082_disconnected-node-dialog.png
>
>
> Because we now have a zero-master clustering paradigm, it's possible to open the UI on a node that is disconnected from the cluster. In this case, changes made to the UI will be accepted, but they will not be replicated to the cluster. As a result, the flow will be out-of-sync with the cluster, and in order to get the node back to the cluster, the changes would have to be undone and the work potentially lost (user could create a template to save the changes but may not know what all they changed).
> The UI should make it very obvious that the node is disconnected and that any changes that made will not be replicated to the cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)