[
https://issues.apache.org/jira/browse/NIFI-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-2082:
-----------------------------
Issue Type: Sub-task (was: Improvement)
Parent: NIFI-2010
> 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
>
>
> 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)
