[
https://issues.apache.org/jira/browse/NIFI-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Gilman updated NIFI-3848:
------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Refresh client's component revision data when node reconnects to cluster
> ------------------------------------------------------------------------
>
> Key: NIFI-3848
> URL: https://issues.apache.org/jira/browse/NIFI-3848
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Affects Versions: 1.1.1
> Reporter: Jeff Storck
> Assignee: Matt Gilman
> Priority: Minor
> Fix For: 1.3.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
