[
https://issues.apache.org/jira/browse/NIFI-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16431140#comment-16431140
]
ASF GitHub Bot commented on NIFI-543:
-------------------------------------
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2509#discussion_r180211928
--- Diff: nifi-docs/src/main/asciidoc/developer-guide.adoc ---
@@ -1751,6 +1751,12 @@ will handle your Processor:
will always be set to `1`. This does *not*, however, mean that
the Processor does not have to be thread-safe,
as the thread that is executing `onTrigger` may change between
invocations.
+ - `PrimaryNodeOnly`: Apache NiFi, when clustered, offers two modes of
execution for Processors: "Primary Node" and
+ "All Nodes". Although running in all the nodes offers better
parallelism, some Processors are known to cause unintended
+ behaviors when run in multiple nodes. For instance, some
Processors lists or reads files from remote filesystems. If such
--- End diff --
Typo in the docs: think it should read "some Processors list or read files"
rather than "lists of reads"
> 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)
