[jira] [Commented] (NIFI-3151) Processors on a Primary Node do not retrieve state changes made by the ZooKeeper Migrator

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

    [ https://issues.apache.org/jira/browse/NIFI-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732667#comment-15732667 ] 

Jeff Storck commented on NIFI-3151:
-----------------------------------

Discussed this with [~markap14].  In processors that store cluster-scoped state, when started (@OnScheduled), they should retrieve state even if the instance of the processor is running on a Primary Node.  Also, this will ensure that the "Clear State" functionality will have its intended function, since it clears the state in ZK but not the actual processor's state.  When the processor is scheduled to run again, it would retrieve the state from ZK (which would be been cleared) and will start with a clear state.

> Processors on a Primary Node do not retrieve state changes made by the ZooKeeper Migrator
> -----------------------------------------------------------------------------------------
>
>                 Key: NIFI-3151
>                 URL: https://issues.apache.org/jira/browse/NIFI-3151
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.1.0
>            Reporter: Jeff Storck
>
> Found when testing the ZooKeeper Migrator.  If a processor running on a primary node has done some processing, and therefore has some state stored in ZK, it will retrieve state from ZK unless the primary node changes.
> In the case of the ZooKeeper Migrator writing new state to ZK, the processor on the primary node will not use this new state, and will continue to process based on its current state.
> When a processor is started, even when it is running on the primary node, it should check to see if there are state differences between its current state and what's in ZK, and if there are differences, it should retrieve that state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)