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!



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to