ASF GitHub Bot commented on NIFI-543:

Github user zenfenan commented on a diff in the pull request:

    --- Diff: 
    @@ -741,8 +742,8 @@
    -                    // show the execution node option if we're cluster or 
we're currently configured to run on the primary node only
    -                    if (nfClusterSummary.isClustered() || executionNode 
=== 'PRIMARY') {
    +                    // show the execution node option if we're clustered 
and execution node is not restricted to run only in primary node
    +                    if (nfClusterSummary.isClustered() && 
executionNodeRestricted !== true) {
    --- End diff --
    No. If we add `executionNode === 'PRIMARY'` then the UI will show the 
dropdown menu for `ExecutionNodes`. Moreover, why should we need the ability to 
change to `All Nodes` in the said scenario because it is running in standalone 
mode, right? Primary Node or All Nodes doesn't make sense in standalone mode. 

> 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

Reply via email to