You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Bryan Bende (Jira)" <ji...@apache.org> on 2022/04/01 18:29:00 UTC

[jira] [Updated] (NIFI-9853) On startup, and when importing flow from registry/file, component states not synchronized properly.

     [ https://issues.apache.org/jira/browse/NIFI-9853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Bende updated NIFI-9853:
------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> On startup, and when importing flow from registry/file, component states not synchronized properly.
> ---------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-9853
>                 URL: https://issues.apache.org/jira/browse/NIFI-9853
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.16.0
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Critical
>             Fix For: 1.16.1
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Prior to 1.16, when a users chose to Save Flow Definition, the exported .json did not contain a state for Controller Services/processors. When a flow was imported, the state defaulted to DISABLED for services, ENABLED/STOPPED for processors.
> In 1.16, though, the exported JSON does contain the scheduled state. When a flow is imported, any Controller Service whose state is marked as ENABLED immediately becomes enabled, but on import it should remain DISABLED.
> Additionally, on startup, if a node inherits the cluster flow, and the cluster flow indicates that a processor should be stopped while the local flow says it should be running, the node allows the processor to continue running, getting out of state with the cluster.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)