You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/07/26 18:38:20 UTC
[jira] [Commented] (NIFI-2318) Node Events shown in cluster table
often indicate that the node's status changed to CONNECTED many times
[ https://issues.apache.org/jira/browse/NIFI-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394295#comment-15394295 ]
ASF subversion and git services commented on NIFI-2318:
-------------------------------------------------------
Commit 52bc23f5dbcc3a236df1fa88744c277e5d60e244 in nifi's branch refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=52bc23f ]
NIFI-2316, NIFI-2318: Ensure that we do not save the flow before initializing the Run Status of components. Clarify the Node Event messages
This closes #678
Signed-off-by: jpercivall <jo...@yahoo.com>
> Node Events shown in cluster table often indicate that the node's status changed to CONNECTED many times
> --------------------------------------------------------------------------------------------------------
>
> Key: NIFI-2318
> URL: https://issues.apache.org/jira/browse/NIFI-2318
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.0.0
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Minor
> Fix For: 1.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)