[
https://issues.apache.org/jira/browse/NIFI-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224454#comment-15224454
]
ASF subversion and git services commented on NIFI-483:
------------------------------------------------------
Commit 1ac05266a5cbab0c05551fc40201376cca13b540 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=1ac0526 ]
NIFI-483: Use ZooKeeper's Leader Election to determine Primary Node. This
closes #301
Signed-off-by: Matt Gilman <[email protected]>
> 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)
