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

[jira] [Assigned] (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:all-tabpanel ]

Matt Gilman reassigned NIFI-2082:
---------------------------------

    Assignee: Matt Gilman

> 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
>            Assignee: Matt Gilman
>            Priority: Critical
>             Fix For: 1.0.0
>
>         Attachments: nifi-2082_cluster-warning.png, nifi-2082_disconnected-node-dialog-2.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)