[NIFI-3848] Refresh client's component revision data when node reconnects to cluster

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.1.1
• Fix Version/s: 1.3.0
• Component/s: Core UI
• Assignee: Matt Gilman
• Reporter: Jeff Storck
• Created: 08/May/17 21:51
• Updated: 17/May/17 13:10
• Resolved: 17/May/17 13:10

Description

If a node is disconnected from the cluster and a component's non-property configuration (ie, a processor's penalty duration) is changed, and the node is reconnected to the cluster, the client that is connected to that node will have a different revision for that component than clients that are connected to other nodes in the cluster.

When a node reconnects to the cluster, clients need a way to react to this event so that they have the correct revision for each component.

NOTE: Current workaround for this issue is to use the browser's refresh button to reload the page.

Issue Links

• relates to: NIFI-1963 Cluster - Flow inheritability
• links to: GitHub Pull Request #1811