You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2016/04/01 21:24:25 UTC

[jira] [Updated] (NIFI-483) Automatically elect a new primary node to allow rolling restarts

     [ https://issues.apache.org/jira/browse/NIFI-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Payne updated NIFI-483:
----------------------------
    Fix Version/s: 1.0.0

> 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
>            Assignee: Mark Payne
>             Fix For: 1.0.0
>
>
> 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)