[
https://issues.apache.org/jira/browse/IMPALA-14267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yida Wu updated IMPALA-14267:
-----------------------------
Labels: admission-control (was: )
> Excessive logging when failing to dequeue queries
> -------------------------------------------------
>
> Key: IMPALA-14267
> URL: https://issues.apache.org/jira/browse/IMPALA-14267
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Reporter: Yida Wu
> Priority: Major
> Labels: admission-control
>
> When the admissiond is at capacity, often due to long-running queries or
> queries that cannot be canceled properly, newly queued queries may not be
> dequeued. In such cases, excessive log messages are repeatedly printed each
> time dequeuing fails. This can result in a large volume of redundant logs
> that provide limited diagnostic value.
> It would be better to improve this by reducing the frequency of these logs,
> especially when the condition could last a long time.
> {code:java}
> I20250723 10:01:56.808945 3705 admission-controller.cc:2679] Could not
> dequeue query id=7c4b6e233a47c50a:6fad07ef00000000 reason: number of running
> queries 1 is at or over limit 1.
> I20250723 10:01:56.908238 3705 admission-controller.cc:2679] Could not
> dequeue query id=7c4b6e233a47c50a:6fad07ef00000000 reason: number of running
> queries 1 is at or over limit 1.
> ...
> I20250723 10:02:00.016685 3705 admission-controller.cc:2679] Could not
> dequeue query id=7c4b6e233a47c50a:6fad07ef00000000 reason: number of running
> queries 1 is at or over limit 1.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
