[ https://issues.apache.org/jira/browse/NIFI-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joseph Witt updated NIFI-2592: ------------------------------ Fix Version/s: 1.1.0 > 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 > Fix For: 1.1.0 > > > 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)