[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gautam Gopalakrishnan updated ZOOKEEPER-1962:
---------------------------------------------
    Attachment: ZOOKEEPER-1962_v4.patch

Apologies for the delay.

[~eribeiro] I had a question about the {{jute.maxbuffer}} suggestion made 
earlier. From what I can understand
- {{jute.maxbuffer}} is a client and server property that ideally is set the 
same
- On the server side, it helps limit the amount of data written into a znode
- On the client side it limits the data that is sent to the server

This {{ls -R}} command runs the {{zk.getChildren()}} call on each child znode 
recursively. If the server-side {{jute.maxbuffer}} limit is breached in any of 
these {{getChildren()}} invocations, then the command will quit with an 
exception. Did we want to artificially limit the output of {{ls -R}} to the 
client limit of {{jute.maxbuffer}} even though it doesn't actually pose a 
problem.

If I've misunderstood the request, please correct me. The patch to address your 
other comments has been attached (v4)

> Add a CLI command to recursively list a znode and children
> ----------------------------------------------------------
>
>                 Key: ZOOKEEPER-1962
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1962
>             Project: ZooKeeper
>          Issue Type: New Feature
>          Components: java client
>    Affects Versions: 3.4.6
>            Reporter: Gautam Gopalakrishnan
>            Assignee: Gautam Gopalakrishnan
>            Priority: Minor
>             Fix For: 3.5.2, 3.6.0
>
>         Attachments: ZOOKEEPER-1962.diff, ZOOKEEPER-1962_v2.patch, 
> ZOOKEEPER-1962_v3.patch, ZOOKEEPER-1962_v4.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> When troubleshooting applications where znodes can be multiple levels deep  
> (eg. HBase replication), it is handy to see all child znodes recursively 
> rather than run an ls for each node manually.
> So I propose adding an option to the "ls" command (-r) which will list all 
> child nodes under a given znode. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to