[
https://issues.apache.org/jira/browse/NIFI-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16459493#comment-16459493
]
ASF GitHub Bot commented on NIFI-543:
-------------------------------------
Github user zenfenan commented on the issue:
https://github.com/apache/nifi/pull/2509
@markap14 I thought about it actually but since `setExecutionNode` gets
called from `FlowController`/`StandardProcessorGroup` but regardless of from
where it gets called they all pass the value from the `ProcessorConfigDTO` to
`setExecutionNode` and since this change takes care of setting the value of
`executionNode` to `PRIMARY` in the DTO, I thought it will be okay. I'll still
add it though to enforce it. But just out of curiosity I'm asking, do you see
any specific scenarios which might make this non-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)
