Github user mcgilman commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2509#discussion_r180888894
--- 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 believe the `executionNode === 'PRIMARY'` was in place to ensure the
currently configured value is shown. If the current value is set to PRIMARY,
but this instance is no longer clustered we need to render that fact. Once the
user reconfigures this value, they will no longer be able to select this option
(since the node isn't clustered and executionNode would be ALL). Hope this
makes sense.
---
