You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (Jira)" <ji...@apache.org> on 2026/01/05 10:36:05 UTC

[jira] [Resolved] (NIFI-2592) Processor still runs @OnScheduled method when it's running on a non-primary node

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

Pierre Villard resolved NIFI-2592.
----------------------------------
    Resolution: Feedback Received

Apache NiFi 1.x is no longer maintained and no new release is planned on the 1.x release line. Marking as resolved as part of a cleanup operation. Please open a new one with an updated description if this is still relevant for NiFi 2.x.

> Processor still runs @OnScheduled method when it's running on a non-primary node
> --------------------------------------------------------------------------------
>
>                 Key: NIFI-2592
>                 URL: https://issues.apache.org/jira/browse/NIFI-2592
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.0.0
>            Reporter: Jeff Storck
>            Priority: Major
>
> If a processor is scheduled to run on the primary node only, the instances of the processor running on non-primary nodes still have their methods annotated with @OnScheduled invoked. The framework should not invoke the @OnScheduled methods if the processor isn't supposed to run on that node.
> To reproduce this, set up a cluster with the nodes running on the same server. The ListenHTTP can be scheduled to be run on the primary node only, but other instances of the processor on non-primary nodes will still try to bind the port, resulting in exceptions.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)