[
https://issues.apache.org/jira/browse/CONNECTORS-921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13964029#comment-13964029
]
Karl Wright commented on CONNECTORS-921:
----------------------------------------
Hi Graeme,
I did originally look at creating a root node for each class of ManifoldCF node
in ZooKeeper. That seemed like it would introduce a lot of overhead, however.
Essentially, the problem is as follows: you have to handle the case, somehow,
where the root node does not exist yet. But you only get one exception
(nodenotfound) whether it's the root node that's missing, or the actual
functional node you are looking for. So you have to do additional work to
disambiguate the two cases.
And, in addition, if you do find that the root node is missing, the root node
must then be created, and in a manner that does not potentially collide with
other threads.
I'd be willing to look into having a *single* persistent root node for all of
ManifoldCF, but I still have concerns that this will cost in performance.
> Refine manifoldcf path in Zookeeper
> -----------------------------------
>
> Key: CONNECTORS-921
> URL: https://issues.apache.org/jira/browse/CONNECTORS-921
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Framework core
> Affects Versions: ManifoldCF 1.6
> Reporter: Graeme Seaton
> Assignee: Graeme Seaton
> Priority: Minor
> Fix For: ManifoldCF 1.6
>
>
> The nodes created in Zookeeper by MCF are created directly beneath the root.
> This can make it difficult to find the nodes for other applications. There
> seems to be a convention to create an application node under the root (based
> on Hbase and Hadoop usage).
> I would like to create a manifoldcf 'parent' and place all of the nodes
> within it. It might also make sense to create 'parent' nodes for each of the
> PATH_PREFIXES.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
