You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Mahadev konar (JIRA)" <ji...@apache.org> on 2010/01/23 01:25:21 UTC

[jira] Commented: (ZOOKEEPER-574) the documentation on snapcount in the admin guide has the wrong default

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

Mahadev konar commented on ZOOKEEPER-574:
-----------------------------------------

+1 the patch looks good.

> the documentation on snapcount in the admin guide has the wrong default
> -----------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-574
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-574
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: documentation
>            Reporter: Patrick Hunt
>            Assignee: Patrick Hunt
>            Priority: Minor
>             Fix For: 3.3.0
>
>         Attachments: ZOOKEEPER-574.patch
>
>
> I believe it's 100k, not 10k
> -----------------------
> snapCount
> (Java system property: zookeeper.snapCount)
> Clients can submit requests faster than ZooKeeper can process them, especially if there are a lot of clients. To prevent ZooKeeper from running out of memory due to queued requests, ZooKeeper will throttle clients so that there is no more than globalOutstandingLimit outstanding requests in the system. The default limit is 1,000.ZooKeeper logs transactions to a transaction log. After snapCount transactions are written to a log file a snapshot is started and a new transaction log file is started. The default snapCount is 10,000.

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