From 3f6610aaf1a7cd3c263e535d7550e5271bc21abc Mon Sep 17 00:00:00 2001 From: Nhi Pham <56242907+demo-kratia@users.noreply.github.com> Date: Mon, 22 May 2023 11:58:17 -0700 Subject: [PATCH] fixed wording in OSS query laning doc (#14324) Co-authored-by: Nhi Pham --- docs/configuration/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuration/index.md b/docs/configuration/index.md index 074aa47b957..abf21428fe0 100644 --- a/docs/configuration/index.md +++ b/docs/configuration/index.md @@ -1801,7 +1801,7 @@ These Broker configurations can be defined in the `broker/runtime.properties` fi |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`, but it is worth noting that like `druid.server.http.enableRequestLimit` is set that query requests over this limit will be denied instead of waiting in the Jetty HTTP request queue.|Unbounded| +|`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`. It is worth noting that when `druid.server.http.enableRequestLimit` is set, query requests over this limit will be denied instead of waiting in the Jetty HTTP request queue.|Unbounded| |`druid.query.scheduler.laning.strategy`|Query laning strategy to use to assign queries to a lane in order to control capacities for certain classes of queries.|`none`| |`druid.query.scheduler.prioritization.strategy`|Query prioritization strategy to automatically assign priorities.|`manual`|