You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by va...@apache.org on 2020/01/16 18:13:11 UTC
[couchdb-documentation] 01/01: Update resharding config section
This is an automated email from the ASF dual-hosted git repository.
vatamane pushed a commit to branch update-resharding-config
in repository https://gitbox.apache.org/repos/asf/couchdb-documentation.git
commit cf98ce060aff329bf34aac5add19b1c70b9596ee
Author: Nick Vatamaniuc <va...@apache.org>
AuthorDate: Thu Jan 16 13:12:22 2020 -0500
Update resharding config section
Some entries were stale and others were missing
---
src/config/resharding.rst | 31 ++++++++++++++++++++++++++++++-
1 file changed, 30 insertions(+), 1 deletion(-)
diff --git a/src/config/resharding.rst b/src/config/resharding.rst
index de91011..3b65e90 100644
--- a/src/config/resharding.rst
+++ b/src/config/resharding.rst
@@ -32,7 +32,17 @@ Resharding Configuration
will start to fail with the ``max_jobs_exceeded`` error::
[reshard]
- max_jobs = 25
+ max_jobs = 48
+
+ .. config:option:: max_history
+
+ The max length of each jobs event log. The history records job starts,
+ stop, retries etc. There is probably not much reason to change this
+ unless use specifies larger number of ``max_retries``::
+
+
+ [reshard]
+ max_history = 20
.. config:option:: max_retries
@@ -77,3 +87,22 @@ Resharding Configuration
[reshard]
source_close_timeout_sec = 600
+
+ .. config:option:: require_node_param
+
+ Require users to specify a ``node`` parameter when creating resharding
+ jobs. This can be used as a safety check to avoid inadvertently
+ starting too many resharding jobs by accident::
+
+
+ [reshard]
+ require_node_param = false
+
+ .. config:option:: require_range_param
+
+ Require users to specify a ``node`` parameter when creating resharding
+ jobs. This can be used as a safety check to avoid inadvertently
+ starting too many resharding jobs by accident::
+
+ [reshard]
+ require_node_param = false