nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Payne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-483) Automatically elect a new primary node to allow rolling restarts
Date Mon, 01 Feb 2016 18:56:39 GMT

    [ https://issues.apache.org/jira/browse/NIFI-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126798#comment-15126798
] 

Mark Payne commented on NIFI-483:
---------------------------------

I think the solution here is not to add a new Scheduling Strategy but rather to divorce the
concepts of "Primary Node Only" and the Scheduling Strategy. I.e., we should have 3 scheduling
strategies: Timer Driven, Event Driven, Cron Driven - and Primary Node Only as a separate
concern.


> 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)

Mime
View raw message