Mahadev konar commented on ZOOKEEPER-119:

i like the idea of having .zookeeper reserved as a proc file system... but we 
need to be a little more cleaner in implementing this ---

1) I htink .zookeeeper should always exist (as a true node) when a database 
from scratch is created. The node is read only for the clients.

2) the response that a client gets should be

on creation of .zookeeper return back node already exists

if the client tries and create children of .zookeeper then we throw out an acl 
and the same with deletion of that node .

> Reserve ".zookeeper" node for server use.
> -----------------------------------------
>                 Key: ZOOKEEPER-119
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-119
>             Project: Zookeeper
>          Issue Type: New Feature
>          Components: server
>            Reporter: Patrick Hunt
>            Assignee: Jakob Homan
>         Attachments: ZOOKEEPER-119.patch
> The server should not allow clients to create .zookeeper nodes in the node 
> hierarchy. These nodes should be reserved for zk future use, some ideas:
> * /.zookeeper/proc
> * /.zookeeper/stats
> * /.zookeeper/...
> * /.../.zookeeper/... (disallow both at root as well as child nodes)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to