Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2509#discussion_r180211409
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/nf/canvas/nf-processor-configuration.js
---
@@ -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 --
I think we still need the executionNode === 'PRIMARY' here:
```
if ((nfClusterSummary.isClustered() && executionNodeRestricted !== true) ||
executionNode === 'PRIMARY') {
```
This way, if running in standalone mode, but the processor is marked with
an ExecutionNode of Primary Node (which may be the case if instantiating a
template from a cluster, or if if copying a flow.xml.gz over or something like
that) we still have the ability to change it to 'All Nodes'.
---
