[
https://issues.apache.org/jira/browse/NIFI-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021498#comment-16021498
]
Matt Gilman commented on NIFI-3922:
-----------------------------------
[~nadih] I have replicated the issue using the 1.2.0 release. I believe the
issue was addressed in this JIRA [1]. It specifically refers to clustered
scenarios but the changes also address the issue with standalone instances. If
possible, please pull down the latest from master and rebuild locally to
verify. I'm going to close this as a duplicate.
Thanks
[1] https://issues.apache.org/jira/browse/NIFI-3900
> Inconsistency in Resume, Stop, Start of Processors/Controller Services
> ----------------------------------------------------------------------
>
> Key: NIFI-3922
> URL: https://issues.apache.org/jira/browse/NIFI-3922
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.2.0
> Reporter: n h
> Attachments: flow.xml.gz, nifi.properties
>
>
> There are some inconsistency in Resume, Stop, Start of Processors/Controller
> Services.
> For Example in rare situation when nifi starts, all processors are stopped
> (not resumed), even if bdfs.flowcontroller.autoResumeState=true
> Also, it is (rarely) seen that when a processor is stopped by rest api, all
> processors are stopped. (the target processor and all others are in root
> group)
> Update: I tried with clean installation and I add 2 processors, connect and
> start them. Then I restart the nifi. Sometimes processors are in running
> state (normal behavior) and sometimes (20% chance) they are stopped.
> flow.xml.gz and nifi.properties are attached
> Env: windows 8.1 64 / java 1.8 x64 update 72
> No error is log files.
> I keep Fix Version 1.3.0 because it is introduced in 1.2.0 version (not seen
> in 1.0.0 and 1.1.0)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
