[
https://issues.apache.org/jira/browse/NIFI-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012917#comment-16012917
]
ASF GitHub Bot commented on NIFI-3848:
--------------------------------------
GitHub user mcgilman opened a pull request:
https://github.com/apache/nifi/pull/1811
NIFI-3848: Overriding revisions when a node's connection to the cluster
changes
NIFI-3848:
- Allowing the revision check to be overridden when the state of a nodes
connection to the cluster changes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mcgilman/nifi NIFI-3848
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1811.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1811
----
commit fddb8fa4eb3c7368f5a5f5ed2d263c9bc4bdf3f4
Author: Matt Gilman <[email protected]>
Date: 2017-05-16T18:37:38Z
NIFI-3848:
- Allowing the revision check to be overridden when the state of a nodes
connection to the cluster changes.
----
> 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
>
> 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)
