[
https://issues.apache.org/jira/browse/KNOX-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13806348#comment-13806348
]
Larry McCay commented on KNOX-145:
----------------------------------
This looks right to me. I agree that the cluster rooted namespace is needed as
well. It provides flexibility for how Zookeeper clusters will be deployed and
utilized in shops with multiple Hadoop clusters.
As for additional bookkeeping, each Knox instance should just pull all the
config on startup.
> 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.4.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.1#6144)
