This is an automated email from the ASF dual-hosted git repository.
vatamane pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/couchdb-documentation.git
The following commit(s) were added to refs/heads/master by this push:
new 5fe62f7 Trying to improve the replication scheduler configuration
parameters (fixes apache/couchdb#344) (#345)
5fe62f7 is described below
commit 5fe62f7b6cb1d4b7b83ffc1e77da3b247dbc4834
Author: Andrea Brancatelli <[email protected]>
AuthorDate: Thu Nov 1 05:41:54 2018 +0100
Trying to improve the replication scheduler configuration parameters (fixes
apache/couchdb#344) (#345)
Improve the replication scheduler configuration parameters
Authored-By: skeyby <[email protected]>
---
src/config/replicator.rst | 30 +++++++++++++++++++-----------
1 file changed, 19 insertions(+), 11 deletions(-)
diff --git a/src/config/replicator.rst b/src/config/replicator.rst
index bf57223..80fc44e 100644
--- a/src/config/replicator.rst
+++ b/src/config/replicator.rst
@@ -27,11 +27,18 @@ Replicator Database Configuration
.. versionadded:: 2.1
- Number of actively running replications. Making this too high could
- cause performance issues. Making it too low could mean replications
- jobs might not have enough time to make progress before getting
- unscheduled again. This parameter can be adjusted at runtime and will
- take effect during next rescheduling cycle::
+ Number of actively running replications.
+ This value represents the threshold to trigger the automatic
replication
+ scheduler.
+ The system will check every ``interval`` milliseconds how many
replication
+ jobs are running, and if there are more than ``max_jobs`` active jobs,
+ the scheduler will pause-and-restart up to ``max_churn`` jobs in the
+ scheduler queue.
+ Making this value too high could cause performance issues, while making
+ it too low could mean replications jobs might not have enough time to
make
+ progress before getting unscheduled again.
+ This parameter can be adjusted at runtime and will take effect during
next
+ rescheduling cycle::
[replicator]
max_jobs = 500
@@ -40,8 +47,9 @@ Replicator Database Configuration
.. versionadded:: 2.1
- Scheduling interval in milliseconds. During each reschedule cycle
- scheduler might start or stop up to "max_churn" number of jobs::
+ Scheduling interval in milliseconds.
+ During each reschedule cycle the scheduler might start or stop up to
``max_churn``
+ number of jobs::
[replicator]
interval = 60000
@@ -50,10 +58,10 @@ Replicator Database Configuration
.. versionadded:: 2.1
- Maximum number of replications to start and stop during rescheduling.
- This parameter along with ``interval`` defines the rate of job
- replacement. During startup, however a much larger number of jobs could
- be started (up to ``max_jobs``) in a short period of time::
+ Maximum number of replication jobs to start and stop during
rescheduling.
+ This parameter, along with ``interval``, defines the rate of job
replacement.
+ During startup, however, a much larger number of jobs could be started
+ (up to ``max_jobs``) in a short period of time::
[replicator]
max_churn = 20
