[
https://issues.apache.org/jira/browse/NIFI-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16402081#comment-16402081
]
Sivaprasanna Sethuraman commented on NIFI-543:
----------------------------------------------
Bryan,
I understand the concern. Valid point. I'll remove the
setExecutionNodeRestricted from StandardProcessorNode. But I don't
understand why executionNodeRestricted boolean has to be moved to
ProcessorDetails. I mean I don't understand the part where you say "
changing from ProcessorXYZ v1 which is @PrimaryNodeOnly to ProcessorXYZ
v2". Which one of the below are you implying?
1. Are you talking about the scenario where NiFi is being upgraded from
one version to another version (or)
2. Are you saying because we are moving executionNodeRestricted to
ProcessorDetails, even older version of the processors which are not
annotated with PrimaryNodeOnly (but their new version counterparts are
annotated), the old version will also be executionNodeRestricted?
Appreciate your inputs. :)
On Thu, Mar 15, 2018 at 11:39 PM, Bryan Bende (JIRA) <[email protected]>
> 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)
