core/sql: admission control tracking issue #38076
Labels
A-admission-control
A-kv
Anything in KV that doesn't belong in a more specific category.
A-kv-client
Relating to the KV client and the KV interface.
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
T-kv
KV Team
T-sql-queries
SQL Queries Team
Admission control limits the rate of query execution across the cluster to levels that the system can handle without significant performance degradation. Once resource limits have been reached, and the cluster is overloaded (e.g. RAM, CPU, I/O, Network), incoming queries must wait to begin execution. These queries are stalled (queued) and are admitted (that is, begin executing) when the resources become available. If the time queries spend in the queue + execution exceed a connection time limit the application requests will no longer be stalled and are outright rejected. DBAs can set when admission control will begin queuing, a maximum number of connections per node, and a query timeout.
This is a tracking issue to support this work.
gz#6246
The text was updated successfully, but these errors were encountered: