jtuglu-netflix commented on code in PR #17900:
URL: https://github.com/apache/druid/pull/17900#discussion_r2053025275


##########
docs/ingestion/supervisor.md:
##########
@@ -69,13 +69,14 @@ You can optionally configure autoscaling behavior for 
ingestion tasks using the
 
 The following table outlines the configuration properties for 
`autoScalerConfig`:
 
-|Property|Description|Required|Default|
-|--------|-----------|--------|-------|
-|`enableTaskAutoScaler`|Enables the autoscaler. If not specified, Druid 
disables the autoscaler even when `autoScalerConfig` is not null.|No|`false`|
-|`taskCountMax`|The maximum number of ingestion tasks. Must be greater than or 
equal to `taskCountMin`. If `taskCountMax` is greater than the number of Kafka 
partitions or Kinesis shards, Druid sets the maximum number of reading tasks to 
the number of Kafka partitions or Kinesis shards and ignores 
`taskCountMax`.|Yes||
-|`taskCountMin`|The minimum number of ingestion tasks. When you enable the 
autoscaler, Druid ignores the value of `taskCount` in `ioConfig` and starts 
with the `taskCountMin` number of tasks to launch.|Yes||
-|`minTriggerScaleActionFrequencyMillis`|The minimum time interval between two 
scale actions.| No|600000|
-|`autoScalerStrategy`|The algorithm of autoscaler. Druid only supports the 
`lagBased` strategy. See [Autoscaler strategy](#autoscaler-strategy) for more 
information.|No|`lagBased`|
+| Property                               | Description                         
                                                                                
                                                                                
                                                                                
                       | Required | Default        |

Review Comment:
   Sure



-- 
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]

Reply via email to