nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ricky Saltzer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-483) Automatically elect a new primary node to allow rolling restarts
Date Thu, 02 Apr 2015 20:36:55 GMT

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

Ricky Saltzer commented on NIFI-483:
------------------------------------

Hey Mark -

Thanks for your response. I understand the concern regarding primary role election, those
things can get very tricky. I was suggesting that the primary node itself would be responsible
for electing a new primary during a clean shutdown or restart. If the node were to lose communication
for some odd reason (like you mentioned), automatic election would not be the case. Would
this kind of behavior suffice, or would there still be edge cases that we'd need to be worried
about?


> 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: New Feature
>            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