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

Hadoop QA commented on ZOOKEEPER-327:
-------------------------------------

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12411622/ZOOKEEPER-327.patch
  against trunk revision 787907.

    +1 @author.  The patch does not contain any @author tags.

    +0 tests included.  The patch appears to be a documentation patch that 
doesn't require tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs warnings.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

    +1 core tests.  The patch passed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: 
http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-vesta.apache.org/132/testReport/
Findbugs warnings: 
http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-vesta.apache.org/132/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-vesta.apache.org/132/console

This message is automatically generated.

> document effects (latency) of storing large amounts of data in znodes
> ---------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-327
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-327
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Patrick Hunt
>            Assignee: Benjamin Reed
>            Priority: Minor
>             Fix For: 3.2.0
>
>         Attachments: ZOOKEEPER-327.patch
>
>
> znodes have max 1mb of data storage. using zk to store large amounts of data 
> can negatively impact latency as seen by clients - the server needs to serve 
> the data. often it's a better idea to store a "token" (say a uri) in the 
> znode pointing to a large data block stored elsewhere (filesystem? memcached, 
> etc...) this offloads zk and reduces latency impact
> we should have details of this in the forrest docs.

-- 
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