[
https://issues.apache.org/jira/browse/NIFI-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16458878#comment-16458878
]
ASF GitHub Bot commented on NIFI-543:
-------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/2509
@zenfenan I think there's also one other detail that I missed. The intent
here, I believe, is not just to default to Primary Node execution mode when the
@PrimaryNodeOnly annotation is present, but to actually enforce that the
processor always use Primary Node execution mode if it has the annotation. Is
that correct? If so, then I think we need to update the setExecutionMode()
method to ignore the provided value and use ExecutionMode.PRIMARY_NODE if the
annotation is present. Otherwise, there is no enforcement guaranteed.
> 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)
