[
https://issues.apache.org/jira/browse/NIFI-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126811#comment-15126811
]
Ricky Saltzer commented on NIFI-483:
------------------------------------
Agreed, it would be less confusing if we stick to 3 standard schedule
strategies, and then have a simple way to define where the execution runs (e.g.
All Nodes, Primary Node).
> Automatically elect a new primary node to allow rolling restarts
> ----------------------------------------------------------------
>
> Key: NIFI-483
> URL: https://issues.apache.org/jira/browse/NIFI-483
> Project: Apache NiFi
> Issue Type: Sub-task
> Reporter: Ricky Saltzer
>
> In a clustered environment, if you restart the primary node's NiFi instance,
> all of the processors scheduled on "Primary Node" will automatically be
> re-executed on start up. This is a problem if you require a processor to only
> execute once per day, for example.
> To get around this, you must manually promote a different node to primary
> before restarting it. I think it would be a worthwhile feature to have the
> primary node automatically elect another node primary if it's being
> restarted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
