techdocsmith commented on a change in pull request #11759:
URL: https://github.com/apache/druid/pull/11759#discussion_r721698073
##########
File path: docs/configuration/index.md
##########
@@ -745,7 +745,7 @@ These Coordinator static configurations can be defined in
the `coordinator/runti
|`druid.coordinator.kill.period`|How often to send kill tasks to the indexing
service. Value must be greater than `druid.coordinator.period.indexingPeriod`.
Only applies if kill is turned on.|P1D (1 Day)|
|`druid.coordinator.kill.durationToRetain`| Do not kill unused segments in
last `durationToRetain`, must be greater or equal to 0. Only applies and MUST
be specified if kill is turned on. Note that default value is invalid.|PT-1S
(-1 seconds)|
|`druid.coordinator.kill.maxSegments`|Kill at most n unused segments per kill
task submission, must be greater than 0. Only applies and MUST be specified if
kill is turned on. Note that default value is invalid.|0|
-|`druid.coordinator.balancer.strategy`|Specify the type of balancing strategy
that the coordinator should use to distribute segments among the historicals.
`cachingCost` is logically equivalent to `cost` but is more CPU-efficient on
large clusters and will replace `cost` in the future versions, users are
invited to try it. Use `diskNormalized` to distribute segments among processes
so that the disks fill up uniformly and use `random` to randomly pick processes
to distribute segments.|`cost`|
+|`druid.coordinator.balancer.strategy`|Specify the type of balancing strategy
that the coordinator should use to distribute segments among the historicals.
`cachingCost` is logically equivalent to `cost` but is more CPU-efficient on
large clusters.|`cost`|
Review comment:
I think this is fine. It just highlights a limits of trying to describe
the different options w/in a table cell. Small nit: `random` picks processes.
Otherwise this works.
--
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]
