[
https://issues.apache.org/jira/browse/NIFI-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16461583#comment-16461583
]
ASF GitHub Bot commented on NIFI-543:
-------------------------------------
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/2509
@zenfenan Yeah I think we're on the same page here. Sorry for the different
suggestions earlier but I think we're ultimately getting it right here...
- `All nodes` should be disabled if the component is marked
`PrimaryNodeOnly` regardless of clustered or standalone. However, I think we
should update the tooltip for this field to indicate that it's applicable when
clustered. When not clustered, `All nodes` and `Primary Node` are effectively
the same thing.
- If a processor has been updated to `PrimaryNodeOnly` and its
configuration was previously `All nodes` it should retain that value initially.
However, given the first bullet above, that option will be disabled and would
only allow the user to update it to `Primary node` going forward.
- The field should be always visible regardless of clustered or standalone.
It will allow folks to build flows which may be deployed in a cluster in the
future. It also allows us to remove some of that unnecessarily complex code
when determining the appropriate visibility.
Thanks
> 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)
