[
https://issues.apache.org/jira/browse/NIFI-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15589608#comment-15589608
]
ASF GitHub Bot commented on NIFI-401:
-------------------------------------
Github user mcgilman commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1117#discussion_r84136870
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/nf/canvas/nf-processor-configuration.js
---
@@ -52,22 +52,6 @@ nf.ProcessorConfiguration = (function () {
});
}
- // conditionally support event driven
- if (nf.Canvas.isClustered()) {
- strategies.push({
- text: 'On primary node',
- value: 'PRIMARY_NODE_ONLY',
- description: 'Processor will be scheduled on the primary
node on an interval defined by the run schedule.'
- });
- } else if (processor.config['schedulingStrategy'] ===
'PRIMARY_NODE_ONLY') {
--- End diff --
I realize that we are deprecating 'Primary Node Only' but I believe we
still need to retain this case to handle existing components with this
configuration. The disabled flag will prevent this option from being selected
again.
> New Scheduling strategy (On primary node - CRON )
> -------------------------------------------------
>
> Key: NIFI-401
> URL: https://issues.apache.org/jira/browse/NIFI-401
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Matthew Clarke
> Priority: Minor
> Attachments: initial prototype .png
>
>
> Currently the only scheduling strategy supported when a processor is set to
> use "On primary Node" is Timer Driven. There should be a second option to
> allow cron driven On primary Node scheduling strategy. This would allow
> users to more control over when a given primary node only processor runs.
> This would prevent these processors from running when configuration changes
> or instance restarts occur.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
