@Rocky when i have resource group queuing enabled, with few classifiers, what happens when, there is a query that doesn't match that classifier?

When resource group queuing is enabled in StarRocks, if a query does not match any of your defined classifiers, the following happens: 1. Fallback to the Default Group: The query is automatically assigned to the default resource group, which is named

default_wg

. 2. Queuing Behavior: Once the query is assigned to

default_wg

, it will be subject to the queuing configuration (like

concurrency_limit

and

max_queued_queries

) defined specifically for that default group. 3. No "Fail on No Match": Currently, StarRocks does not support forcing a query to fail if it doesn't match a user-defined classifier; the fallback to

default_wg

is mandatory. Key Details about `default_wg`: * Resource Limits: By default,

default_wg

is configured to use all available CPU cores (

cpu_core_limit

) and 100% of the memory limit (

mem_limit

) unless you manually modify it. * Checking Assignments: You can verify which resource group a query was assigned to by checking the

ResourceGroup

column in the

fe.audit.log

or by running

EXPLAIN VERBOSE <your_query>

. Recommendation: Since all non-matching queries land in

default_wg

, it is a good practice to configure

concurrency_limit

and

max_queued_queries

for

default_wg

as well. This prevents "unclassified" queries from overwhelming the system and ensures they also follow your desired queuing logic. References • faq/resource_isolation_faq.md • administration/management/resource_management/resource_group.md