[
https://issues.apache.org/jira/browse/NIFI-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377297#comment-16377297
]
Mark Payne commented on NIFI-543:
---------------------------------
[~sivaprasanna] thanks for jumping in! Yes, I think we want to disable the
"Execution Node" configuration option all together if the processor is marked
as PrimaryNodeOnly. There are certainly Processors for which Primary Node Only
makes sense sometimes and All Nodes makes sense sometimes (ListFile is an
example of this). Such processors should not use this annotation. But for other
processors, it should only ever run on Primary Node in a cluster. An example of
this would be GetJMSTopic. If you have 5 nodes in a cluster running this, then
all 5 nodes will get a copy of the same message. This is not the intended
behavior and should not be allowed. So that processor would be a great
candidate for this annotation.
> Provide extensions a way to indicate that they can run only on primary node,
> if clustered
> -----------------------------------------------------------------------------------------
>
> Key: NIFI-543
> URL: https://issues.apache.org/jira/browse/NIFI-543
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core Framework, Documentation & Website, Extensions
> Reporter: Mark Payne
> Assignee: Sivaprasanna Sethuraman
> Priority: Major
>
> There are Processors that are known to be problematic if run from multiple
> nodes simultaneously. These processors should be able to use a
> @PrimaryNodeOnly annotation (or something similar) to indicate that they can
> be scheduled to run only on primary node if run in a cluster.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
