techdocsmith commented on a change in pull request #11444:
URL: https://github.com/apache/druid/pull/11444#discussion_r673173588
##########
File path: docs/configuration/index.md
##########
@@ -1015,7 +1015,7 @@ There are additional configs for autoscaling (if it is
enabled):
|`druid.indexer.autoscale.pendingTaskTimeout`|How long a task can be in
"pending" state before the Overlord tries to scale up.|PT30S|
|`druid.indexer.autoscale.workerVersion`|If set, will only create nodes of set
version during autoscaling. Overrides dynamic configuration. |null|
|`druid.indexer.autoscale.workerPort`|The port that MiddleManagers will run
on.|8080|
-|`druid.indexer.autoscale.workerCapacityHint`| Worker capacity for determining
the number of workers needed for auto scaling when there is currently no worker
running. If unset or set to value of 0 or less, auto scaler will scale to
`minNumWorkers` in autoScaler config instead. This value should typically be
equal to `druid.worker.capacity` when you have a homogeneous cluster and the
average of `druid.worker.capacity` across the workers when you have a
heterogeneous cluster. Note: this config is only applicable to
`pendingTaskBased` provisioning strategy|-1|
+|`druid.indexer.autoscale.workerCapacityHint`| A estimation of the number of
task slots available for each worker launched by the auto scaler when there are
no workers running. The auto scaler uses the worker capacity hint to launch
workers with an adequate capacity to handle pending tasks. When unset or set to
a value less than or equal to 0, the auto scaler scales workers equal to the
value for `minNumWorkers` in autoScaler config instead. The auto scaler assumes
that each worker, either a middleManager or indexer, has the same amount of
task slots. Therefore, when all your workers have the same capacity
(homogeneous capacity), set the value for `autoscale.workerCapacityHint` equal
to `druid.worker.capacity`. If your workers have different capacities
(heterogeneous capacity), set the value to the average of
`druid.worker.capacity` across the workers. For example, if two workers have
`druid.worker.capacity=10`, and one has `druid.worker.capacity=4`, set
`autoscale.workerCapacityHin
t=8`. Only applies to `pendingTaskBased` provisioning strategy.|-1|
Review comment:
```suggestion
|`druid.indexer.autoscale.workerCapacityHint`| An estimation of the number
of task slots available for each worker launched by the auto scaler when there
are no workers running. The auto scaler uses the worker capacity hint to launch
workers with an adequate capacity to handle pending tasks. When unset or set to
a value less than or equal to 0, the auto scaler scales workers equal to the
value for `minNumWorkers` in autoScaler config instead. The auto scaler assumes
that each worker, either a middleManager or indexer, has the same amount of
task slots. Therefore, when all your workers have the same capacity
(homogeneous capacity), set the value for `autoscale.workerCapacityHint` equal
to `druid.worker.capacity`. If your workers have different capacities
(heterogeneous capacity), set the value to the average of
`druid.worker.capacity` across the workers. For example, if two workers have
`druid.worker.capacity=10`, and one has `druid.worker.capacity=4`, set
`autoscale.workerCapacity
Hint=8`. Only applies to `pendingTaskBased` provisioning strategy.|-1|
```
--
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]
