You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2009/11/11 01:45:27 UTC
[jira] Created: (ZOOKEEPER-574) the documentation on snapcount in
the admin guide has the wrong default
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
Reporter: Patrick Hunt
Priority: Minor
Fix For: 3.3.0
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.
[jira] Updated: (ZOOKEEPER-574) the documentation on snapcount in
the admin guide has the wrong default
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-574:
-----------------------------------
Component/s: documentation
Assignee: Patrick Hunt
> 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.
[jira] Updated: (ZOOKEEPER-574) the documentation on snapcount in
the admin guide has the wrong default
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-574:
-----------------------------------
Status: Patch Available (was: Open)
> 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.
[jira] Updated: (ZOOKEEPER-574) the documentation on snapcount in
the admin guide has the wrong default
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-574:
-----------------------------------
Attachment: ZOOKEEPER-574.patch
fixed documentation with correct default for snapcount
also fixed what looked like a typo in the docs - seems some text from another parameter was incorrectly
copied for this parameter. I think I fixed this by removing the unneccessary text (it's copied from another
param in that same document)
> 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
> 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.
[jira] Commented: (ZOOKEEPER-574) the documentation on snapcount in
the admin guide has the wrong default
Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (ZOOKEEPER-574) the documentation on snapcount in
the admin guide has the wrong default
Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar updated ZOOKEEPER-574:
------------------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
I just committed this. thanks pat.
> 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.