You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Jonathan Hsieh (JIRA)" <ji...@apache.org> on 2011/08/25 22:54:39 UTC

[jira] [Commented] (ZOOKEEPER-1162) consistent handling of jute.maxbuffer when attempting to read large zk "directories"

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091323#comment-13091323 ] 

Jonathan Hsieh commented on ZOOKEEPER-1162:
-------------------------------------------

Basically, I feel that to be consistent behavior-wise it should either:

1) reject on write when dir becomes too big, keeping the current read constraint (ideally in zk, as opposed to the client)
2) accept write like currently but allow the read to then succeed in this particular case.  
3) warn when writing when it gets too big, and then allow reads to succeed even if too big.  

> consistent handling of jute.maxbuffer when attempting to read large zk "directories"
> ------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1162
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1162
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.3.3
>            Reporter: Jonathan Hsieh
>            Priority: Critical
>             Fix For: 3.5.0
>
>
> Recently we encountered a sitaution where a zk directory got sucessfully populated with 250k elements.  When our system attempted to read the znode dir, it failed because the contents of the dir exceeded the default 1mb jute.maxbuffer limit.  There were a few odd things
> 1) It seems odd that we could populate to be very large but could not read the listing 
> 2) The workaround was bumping up jute.maxbuffer on the client side setting.
> Would it make more sense to have it reject adding new znodes if it exceeds jute.maxbuffer? 
> Alternately, would it make sense to have zk dir listing ignore the jute.maxbuffer setting?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira