You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Jeff Storck (JIRA)" <ji...@apache.org> on 2016/08/17 19:44:20 UTC

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

Jeff Storck created NIFI-2592:
---------------------------------

             Summary: 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


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
(v6.3.4#6332)