[
https://issues.apache.org/jira/browse/NIFI-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377038#comment-16377038
]
Sivaprasanna Sethuraman commented on NIFI-543:
----------------------------------------------
[~markap14], [~bende], I've started working on this and right now it is like
this: If a processor is marked with this annotation, during instantiating, the
executionNode is set to 'PRIMARY'. This can however be changed later in the UI
through the configuration menu. Are we looking at completely disabling the
Execution Node configuration option and make the processor run only on Primary
Node which makes more sense to me but also feels like restricting the user's
freedom. So wanted to get the community's opinion on this.
> 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)
