[
https://issues.apache.org/jira/browse/NIFI-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16431141#comment-16431141
]
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_r180211507
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/nf/nf-processor-details.js
---
@@ -215,9 +215,10 @@
}
var executionNode = details.config['executionNode'];
+ var executionNodeRestricted =
details.executionNodeRestricted
// only show the execution-node when applicable
- if (nfClusterSummary.isClustered() || executionNode
=== 'PRIMARY') {
+ if (nfClusterSummary.isClustered() &&
executionNodeRestricted !== true) {
--- End diff --
I think we need the executionNode === 'PRIMARY' to still be considered here
as well.
> 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)
