ccaominh commented on a change in pull request #9407: query laning and load
shedding
URL: https://github.com/apache/druid/pull/9407#discussion_r387962715
##########
File path: docs/configuration/index.md
##########
@@ -1476,9 +1476,31 @@ These Broker configurations can be defined in the
`broker/runtime.properties` fi
|`druid.broker.select.tier`|`highestPriority`, `lowestPriority`, `custom`|If
segments are cross-replicated across tiers in a cluster, you can tell the
broker to prefer to select segments in a tier with a certain
priority.|`highestPriority`|
|`druid.broker.select.tier.custom.priorities`|`An array of integer
priorities.`|Select servers in tiers with a custom priority list.|None|
+##### Query laning
+
+The Broker provides facilities to aid in query capacity reservation for
heterogeneous query workloads in the form of 'laning' strategies, which provide
a variety of mechanisms to examine and classify a query, assigning it to a
'lane'. Lanes are defined with capacity limits which the broker will enforce,
causing requests in excess of the capacity to be discarded with an HTTP 429
status code, reserving resources for other lanes or for interactive queries
(with no lane).
+
+|Property|Description|Default|
+|--------|-----------|-------|
+|`druid.query.scheduler.numThreads`|Maximum number of HTTP threads to dedicate
to query processing. To save HTTP thread capacity, this should be lower than
`druid.server.http.numThreads`.|Unbounded|
+|`druid.query.scheduler.laning.type`|Query laning strategy to use to assign
queries to a lane in order to control capacities for certain classes of
queries.|`none`|
Review comment:
Perhaps the setting name ("type") and the name in the docs ("strategy")
should be made consistent.
In terms of documentation flow, it may be helpful to add a section below
(e.g. "Laning strategy") and reference it here. "No laning strategy", etc.
would be children on this new section.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
