nkalmar commented on a change in pull request #905: ZOOKEEPER-3359: Batch
commits in the CommitProcessor
URL: https://github.com/apache/zookeeper/pull/905#discussion_r290656383
##########
File path: zookeeper-docs/src/main/resources/markdown/zookeeperAdmin.md
##########
@@ -1358,6 +1358,19 @@ Both subsystems need to have sufficient amount of
threads to achieve peak read t
Number of Commit Processor worker threads. If configured with 0 worker
threads, the main thread
will process the request directly. The default value is the number of cpu
cores.
+* *zookeeper.commitProcessor.maxReadBatchSize* :
+ (Java system property only: **zookeeper.commitProcessor.maxReadBatchSize**)
+ Max number of reads to process from queuedRequests before switching to
processing commits.
+ If the value < 0 (default), we switch whenever we have a local write, and
pending commits.
+ A high read batch size will delay commit processing, causing stale data to
be served.
+
+* *zookeeper.commitProcessor.maxCommitBatchSize* :
Review comment:
Same here, some general guide if possible.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
