[
https://issues.apache.org/jira/browse/NIFI-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402867#comment-15402867
]
ASF GitHub Bot commented on NIFI-2078:
--------------------------------------
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/563
Also I'm not sure if this is due to Kafka or our implementation but it
seems the offsets for GetKafka don't get updated until the processor is
stopped. I will start it, after a while it will have processed some data but
when I view the state I see nothing. As soon as I stop it and view the state I
see the offsets. In the ZK output I see these 4 statements each time state is
requested:
[2016-08-01 17:31:50,591] INFO Accepted socket connection from
/127.0.0.1:59809 (org.apache.zookeeper.server.NIOServerCnxnFactory)
[2016-08-01 17:31:50,591] INFO Client attempting to establish new session
at /127.0.0.1:59809 (org.apache.zookeeper.server.ZooKeeperServer)
[2016-08-01 17:31:50,593] INFO Established session 0x15647e175570031 with
negotiated timeout 30000 for client /127.0.0.1:59809
(org.apache.zookeeper.server.ZooKeeperServer)
[2016-08-01 17:31:50,597] INFO Processed session termination for sessionid:
0x15647e175570031 (org.apache.zookeeper.server.PrepRequestProcessor)
[2016-08-01 17:31:50,598] INFO Closed socket connection for client
/127.0.0.1:59809 which had sessionid 0x15647e175570031
(org.apache.zookeeper.server.NIOServerCnxn)
> State management for processors whose states are managed externally
> -------------------------------------------------------------------
>
> Key: NIFI-2078
> URL: https://issues.apache.org/jira/browse/NIFI-2078
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Koji Kawamura
> Assignee: Koji Kawamura
> Fix For: 1.0.0
>
>
> Inherently by the nature of a given processor it may involve state managed by
> itself (using nifi state management), or can be managed by some external
> service it interacts with (kafka's offset), and theoretically some might have
> both going on. With the new state management, we're giving users a way to
> reset state managed by nifi for a given processor. But it doesnt apply to
> those processors who have external state.
> we should consider offering a way to reset state that allows a processor to
> call out to whatever external store it impacts
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
