Hi, I am looking into load shedding, and right now am not using query laning on the broker, I noticed an odd behavior in testing where it seems when both

druid.server.http.numThreads

and

druid.query.scheduler.numThreads

, it seems the former enforces when 429s will be returned (enableRequestLimit=true here), but I found in the code this enableRequestQueuing that is not documented that when we set to false manually (by default its true), we get the

scheduler.numThreads

being used as the limit after which 429s are returned. I just wanted to know: 1. Why is this flag not documented, and why is it intended to be removed? I am thinking we would want to enforce limit at the scheduler number because we would always want some capacity of threads avaialble for health checks and to return a 429 to the router - but do let me know if I'm missing something here with how load shedding can be done on the broker 2. On load shedding, would we want the historicals to return a 429, or is that a bad practice? Wondering if that could cause the overall query to fail at the broker or even the broker response to be incomplete