You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2017/05/17 13:33:04 UTC

[jira] [Updated] (NIFI-3923) When clustered, nodes can start processors before repositories have finished initializing

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

Mark Payne updated NIFI-3923:
-----------------------------
    Status: Patch Available  (was: Open)

> When clustered, nodes can start processors before repositories have finished initializing
> -----------------------------------------------------------------------------------------
>
>                 Key: NIFI-3923
>                 URL: https://issues.apache.org/jira/browse/NIFI-3923
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>
> When a node starts up, if configured to be part of a cluster, the StandardFlowSynchronizer starts/stops processors by calling ProcessGroup.startProcessor and ProcessGroup.stopProcessor instead of going through the FlowController. This can result in a Processor being started before the Provenance/FlowFile/Content Repositories are fully initialized. We should only be starting or stopping Processors through the FlowController.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)