***UNCHECKED*** [jira] [Assigned] (NIFI-4089) Allow standalone NiFi to use ZooKeeper

["Jeff Storck (JIRA)" <ji...@apache.org>]

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

Jeff Storck reassigned NIFI-4089:
---------------------------------

    Assignee: Jeff Storck

> Allow standalone NiFi to use ZooKeeper
> --------------------------------------
>
>                 Key: NIFI-4089
>                 URL: https://issues.apache.org/jira/browse/NIFI-4089
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 1.3.0
>            Reporter: Jeff Storck
>            Assignee: Jeff Storck
>            Priority: Minor
>
> NiFi, when running standalone, will not start an embedded ZooKeeper, and will ignore configuration to use an external ZooKeeper.  While this saves the user from doing extra setup and conserves resources of the host on which NiFi is running when not running in a cluster, it may make moving this standalone node into a cluster more difficult since local state is not migrated to ZK.  This may cause data to be reprocessed, since the most recent state of processing would not be present in ZK.
> If a user plans on eventually expanding a standalone NiFi into a cluster, it would be beneficial to allow a standalone NiFi to use ZK for as a state provider to make adding nodes to create a cluster easier.
> NIFI-4088 would be helpful in the scenario of migrating from a standalone NiFi to a cluster by allowing the migration of local state to ZK.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)