[
https://issues.apache.org/jira/browse/KNOX-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Larry McCay resolved KNOX-145.
------------------------------
Resolution: Won't Fix
Not convinced that this is the right direction due to dependency on ZK and
eventual consensus nature of ZK.
> Integrate with ZooKeeper for config and topology syncronization
> ---------------------------------------------------------------
>
> Key: KNOX-145
> URL: https://issues.apache.org/jira/browse/KNOX-145
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Affects Versions: 0.3.0
> Reporter: Kevin Minder
> Fix For: 0.5.0
>
>
> We should consider using ZooKeeper for config and topo sync. In this model
> Ambari would publish changes to one or more ZK nodes. These changes would be
> detected by each Knox instance. The changes would be written to local disk
> and then "activated". Some changes might require server restart which would
> not be ideal. Ideally all changes could be applied without starting the
> server. This must be the case for topo changes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
