[
https://issues.apache.org/jira/browse/NIFI-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124216#comment-15124216
]
Matt Gilman commented on NIFI-259:
----------------------------------
With the introduction of the QuorumPeer [1] we are no longer able to stand up a
single embedded ZooKeeper instance. This should be a valid state when having a
NiFi cluster with less than three nodes. When using three or more nodes we
should be launching more than one embedded ZooKeeper (for instance, one per
node on a cluster size of 3).
I will re-introduce the usage of ZooKeeperServer when there is only a single
server line in the zookeeper.properties.
[1]
https://github.com/apache/nifi/commit/329e1fe2f4f17832d38e5058f39cef483bde986c
> Framework should offer Processors/extensions a way to manage simple state
> -------------------------------------------------------------------------
>
> Key: NIFI-259
> URL: https://issues.apache.org/jira/browse/NIFI-259
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core Framework
> Reporter: Joseph Witt
> Assignee: Mark Payne
> Fix For: 0.5.0
>
> Attachments: error-message.png
>
>
> It is not uncommon for processors to need managed state which persists
> across restarts. One good example of this is the GetHTTP processor which
> needs to save state of the last cache/e-tag information it received from the
> server it interacts with so that it can avoid constantly pulling an unchanged
> resource.
> Rather than making processors roll their own persistant state management
> perhaps we can offer something to them via the ProcessContext which will
> allow them to save simple primitive values and limited length Strings which
> are local to that node and which are local to that processor only.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
