Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.0.0
-
None
-
None
Description
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.
Attachments
Issue Links
- relates to
-
NIFI-6677 ListHDFS can clear state and re-list everything on Primary Node change if property was modified before Processor started
- Resolved
-
NIFI-6905 GetTwitter processor, configured to run on primary node only, initializes connection to Twitter API from every NiFi cluster node, even on non-primary nodes
- Resolved
-
NIFI-6678 Introduce a notion on `PropertyDescriptor` that indicates that any change to the property should reset component's state
- Open