[
https://issues.apache.org/jira/browse/NIFI-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208845#comment-15208845
]
ASF GitHub Bot commented on NIFI-483:
-------------------------------------
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/301
NIFI-483: Use ZooKeeper Leader Election to Auto-Elect Primary Node
NIFI-483: Use ZooKeeper Leader Election to Auto-Elect Primary Node
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markap14/nifi NIFI-483
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/301.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #301
----
commit 0fa0c5f559974a0cc1d5e3f6bdc914f1bc5d1853
Author: Mark Payne <[email protected]>
Date: 2016-03-23T17:16:13Z
NIFI-483: Use ZooKeeper's Leader Election to determine 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)
