[
https://issues.apache.org/jira/browse/NIFI-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15331955#comment-15331955
]
ASF GitHub Bot commented on NIFI-1997:
--------------------------------------
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/520#discussion_r67190819
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-cluster-protocol/src/main/java/org/apache/nifi/cluster/protocol/jaxb/message/AdaptedDataFlow.java
---
@@ -23,8 +23,6 @@
private byte[] flow;
private byte[] snippets;
- private boolean autoStartProcessors;
-
public AdaptedDataFlow() {
}
--- End diff --
Ohhh... I am sorry - I thought you were commented on the removal of the
'autoStartProcessors' field, and asking why it was there to begin with. I can
remove it if you prefer.
> On restart, a node that joins cluster does not update processors' run state
> to match the cluster
> ------------------------------------------------------------------------------------------------
>
> Key: NIFI-1997
> URL: https://issues.apache.org/jira/browse/NIFI-1997
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Blocker
> Fix For: 1.0.0
>
>
> If I have a cluster, I can disconnect a node from the cluster and stop a
> Processor. If I then re-join the node to the cluster, it will start running
> the processor again, as it should.
> However, if I disconnect a node from the cluster and stop a Processor, and
> then restart that node instead of joining it back into the cluster, the
> problem arises. The node restarts and joins the cluster successfully but does
> not start the Processor that is currently stopped.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
