This is an automated email from the ASF dual-hosted git repository.
kfaraz pushed a commit to branch 25.0.0
in repository https://gitbox.apache.org/repos/asf/druid.git
The following commit(s) were added to refs/heads/25.0.0 by this push:
new 7d106e4360 Docs: Update docs for coordinator dynamic config (#13494)
(#13495)
7d106e4360 is described below
commit 7d106e436011f376bd706871a5029122a8612679
Author: Kashif Faraz <[email protected]>
AuthorDate: Tue Dec 6 13:45:17 2022 +0530
Docs: Update docs for coordinator dynamic config (#13494) (#13495)
* Update docs for useBatchedSegmentSampler
* Update docs for round robin assigment
---
docs/configuration/index.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/docs/configuration/index.md b/docs/configuration/index.md
index 8ac9382b7e..9d4d240004 100644
--- a/docs/configuration/index.md
+++ b/docs/configuration/index.md
@@ -939,7 +939,7 @@ Issuing a GET request at the same URL will return the spec
that is currently in
|`mergeBytesLimit`|The maximum total uncompressed size in bytes of segments to
merge.|524288000L|
|`mergeSegmentsLimit`|The maximum number of segments that can be in a single
[append task](../ingestion/tasks.md).|100|
|`maxSegmentsToMove`|The maximum number of segments that can be moved at any
given time.|5|
-|`useBatchedSegmentSampler`|Boolean flag for whether or not we should use the
Reservoir Sampling with a reservoir of size k instead of fixed size 1 to pick
segments to move. This option can be enabled to speed up segment balancing
process, especially if there are huge number of segments in the cluster or if
there are too many segments to move.|false|
+|`useBatchedSegmentSampler`|Deprecated. Boolean flag for whether or not we
should use the Reservoir Sampling with a reservoir of size k instead of fixed
size 1 to pick segments to move. This option can be enabled to speed up the
sampling of segments to be balanced, especially if there is a large number of
segments in the cluster or if there are too many segments to move.|true|
|`percentOfSegmentsToConsiderPerMove`|Deprecated. This will eventually be
phased out by the batched segment sampler. You can enable the batched segment
sampler now by setting the dynamic Coordinator config,
`useBatchedSegmentSampler`, to `true`. Note that if you choose to enable the
batched segment sampler, `percentOfSegmentsToConsiderPerMove` will no longer
have any effect on balancing. If `useBatchedSegmentSampler == false`, this
config defines the percentage of the total number of seg [...]
|`replicantLifetime`|The maximum number of Coordinator runs for a segment to
be replicated before we start alerting.|15|
|`replicationThrottleLimit`|The maximum number of segments that can be
replicated at one time.|10|
@@ -948,6 +948,7 @@ Issuing a GET request at the same URL will return the spec
that is currently in
|`killDataSourceWhitelist`|List of specific data sources for which kill tasks
are sent if property `druid.coordinator.kill.on` is true. This can be a list of
comma-separated data source names or a JSON array.|none|
|`killPendingSegmentsSkipList`|List of data sources for which pendingSegments
are _NOT_ cleaned up if property `druid.coordinator.kill.pendingSegments.on` is
true. This can be a list of comma-separated data sources or a JSON array.|none|
|`maxSegmentsInNodeLoadingQueue`|The maximum number of segments that could be
queued for loading to any given server. This parameter could be used to speed
up segments loading process, especially if there are "slow" nodes in the
cluster (with low loading speed) or if too much segments scheduled to be
replicated to some particular node (faster loading could be preferred to better
segments distribution). Desired value depends on segments loading speed,
acceptable replication time and numbe [...]
+|`useRoundRobinSegmentAssignment`|Boolean flag for whether segments should be
assigned to historicals in a round robin fashion. When disabled, segment
assignment is done using the chosen balancer strategy. When enabled, this can
speed up segment assignments leaving balancing to move the segments to their
optimal locations (based on the balancer strategy) lazily. |false|
|`decommissioningNodes`| List of historical servers to 'decommission'.
Coordinator will not assign new segments to 'decommissioning' servers, and
segments will be moved away from them to be placed on non-decommissioning
servers at the maximum rate specified by
`decommissioningMaxPercentOfMaxSegmentsToMove`.|none|
|`decommissioningMaxPercentOfMaxSegmentsToMove`| Upper limit of segments the
Coordinator can move from decommissioning servers to active non-decommissioning
servers during a single run. This value is relative to the total maximum number
of segments that can be moved at any given time based upon the value of
`maxSegmentsToMove`.<br /><br />If
`decommissioningMaxPercentOfMaxSegmentsToMove` is 0, the Coordinator does not
move segments to decommissioning servers, effectively putting them in [...]
|`pauseCoordination`| Boolean flag for whether or not the coordinator should
execute its various duties of coordinating the cluster. Setting this to true
essentially pauses all coordination work while allowing the API to remain up.
Duties that are paused include all classes that implement the `CoordinatorDuty`
Interface. Such duties include: Segment balancing, Segment compaction, Emission
of metrics controlled by the dynamic coordinator config `emitBalancingStats`,
Submitting kill tasks [...]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
