[
https://issues.apache.org/jira/browse/NIFI-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122437#comment-15122437
]
Aldrin Piri commented on NIFI-259:
----------------------------------
In the log of the nodes, I don't see any errors that are mapping to this, but
there is the following line that references the associated port:
{code}
2016-01-28 16:22:39,560 INFO [NiFi Web Server-83]
org.apache.zookeeper.ZooKeeper Initiating client connection,
connectString="localhost:1181,localhost:2181,localhost:3181"
sessionTimeout=30000
watcher=org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider$1@77ad6838
{code}
> 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)
