[jira] [Commented] (NIFI-2078) State management for processors whose states are managed externally

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2078:
--------------------------------------

Github user ijokarumawak commented on the issue:

    https://github.com/apache/nifi/pull/563
  
    Hello @JPercivall @olegz @markap14 I've updated Cluster and External state 
behavior in a NiFi cluster, so that only a Primary node access Zookeeper or 
External data store. 
    
    Tested, with the latest master branch. Would you be able to resume review 
process for this?
    
    Now this PR contains three related JIRA issues:
    - [NIFI-2078](https://issues.apache.org/jira/browse/NIFI-2078): State 
managed externally
    - [NIFI-2363](https://issues.apache.org/jira/browse/NIFI-2363): CLUSTER 
scope should be managed on primary node
    - [NIFI-2364](https://issues.apache.org/jira/browse/NIFI-2364): Avoid being 
disconnected by error related to external system
    
    Code change summaries for each topic is written in the commit message.
    
    For External state, it's also possible to make the state external local 
(per node). Please see following screenshots, fig-1 and 2.
    
    fig-1: External - CLUSTER
    ![External - 
CLUSTER](https://cloud.githubusercontent.com/assets/1107620/17093451/5be50578-5284-11e6-8c74-f370a75c43da.png)
    
    fig-2: External - LOCAL, GetKafka in this image is just an example. The 
actual code uses External - CLUSTER scope. There's no implementation using 
External - LOCAL as of now
    ![External - 
LOCAL](https://cloud.githubusercontent.com/assets/1107620/17093484/7f60e3dc-5284-11e6-87cc-b0acc0c4a861.png)
    
    Thanks!



> 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)