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

• Type: Sub-task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.0.0, 1.0.0-Beta
• Component/s: Core UI
• Assignee: Matt Gilman
• Reporter: Mark Payne
• Created: 22/Jun/16 15:05
• Updated: 04/Aug/16 21:24
• Resolved: 14/Jul/16 15:34

Description

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.

Issue Links

• is related to: NIFI-1947 Update Cluster Awareness