Yida Wu created IMPALA-12645:
--------------------------------
Summary: Improve logging information for Impala-Service-Pool
rejection
Key: IMPALA-12645
URL: https://issues.apache.org/jira/browse/IMPALA-12645
Project: IMPALA
Issue Type: Improvement
Components: Backend
Reporter: Yida Wu
Came across cases showing the unusual logs like below, it is weird that the
impala-service-pool has 0 item and consumes 0 memory but rejects the request.
{code:java}
Service unavailable: ExecQueryFInstances request on impala.ControlService from
xxx.xxx.xxx.xxx:xxxx dropped due to backpressure. The service queue contains 0
items out of a maximum of 2147483647; memory consumption is 0.
{code}
There's a possibility that the printed memory consumption is inaccurate. This
discrepancy may occur because the lock responsible for the memory tracker is
released before printing. It would be beneficial to review this behavior,
ensuring that the logs provide an accurate representation of memory consumption
for debugging purposes.
Lock released:
https://github.com/apache/impala/blob/a6de494f24c47fbd679a037341ae0a34b9f696ff/be/src/rpc/impala-service-pool.cc#L195
Printing:
https://github.com/apache/impala/blob/a6de494f24c47fbd679a037341ae0a34b9f696ff/be/src/rpc/impala-service-pool.cc#L140
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
