a2l007 commented on a change in pull request #11960:
URL: https://github.com/apache/druid/pull/11960#discussion_r755332953
##########
File path: docs/configuration/index.md
##########
@@ -886,7 +886,7 @@ Issuing a GET request at the same URL will return the spec
that is currently in
|`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|
-|`percentOfSegmentsToConsiderPerMove`|The percentage of the total number of
segments in the cluster that are considered every time a segment needs to be
selected for a move. Druid orders servers by available capacity ascending (the
least available capacity first) and then iterates over the servers. For each
server, Druid iterates over the segments on the server, considering them for
moving. The default config of 100% means that every segment on every server is
a candidate to be moved. This should make sense for most small to medium-sized
clusters. However, an admin may find it preferable to drop this value lower if
they don't think that it is worthwhile to consider every single segment in the
cluster each time it is looking for a segment to move.|100|
+|`percentOfSegmentsToConsiderPerMove`|Deprecated. Will eventually be phased
out by the batched segment sampler. Only used if `useBatchedSegmentSampler ==
false`. The percentage of the total number of segments in the cluster that are
considered every time a segment needs to be selected for a move. Druid orders
servers by available capacity ascending (the least available capacity first)
and then iterates over the servers. For each server, Druid iterates over the
segments on the server, considering them for moving. The default config of 100%
means that every segment on every server is a candidate to be moved. This
should make sense for most small to medium-sized clusters. However, an admin
may find it preferable to drop this value lower if they don't think that it is
worthwhile to consider every single segment in the cluster each time it is
looking for a segment to move.|100|
Review comment:
Should we add a similar deprecation message in the web console
description for this property?
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
