You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "wesleydeng (Jira)" <ji...@apache.org> on 2021/03/10 12:04:00 UTC
[jira] [Created] (IMPALA-10578) Big Query influence other query
seriously when hardware not reach limit
wesleydeng created IMPALA-10578:
-----------------------------------
Summary: Big Query influence other query seriously when hardware not reach limit
Key: IMPALA-10578
URL: https://issues.apache.org/jira/browse/IMPALA-10578
Project: IMPALA
Issue Type: Bug
Components: Backend
Affects Versions: Impala 3.4.0
Environment: impala-3.4
80 machines with 96 cpu and 256GB mem
Reporter: wesleydeng
Attachments: image-2021-03-10-19-59-24-188.png
When a big query is running, other query is very difficult to start. From the impalad log, I found a incomprehensible log like this:
!https://iwiki.woa.com/download/attachments/584684948/image2021-3-10_17-4-33.png?version=1&modificationDate=1615367074000&api=v2!
!image-2021-03-10-19-59-24-188.png!
When the Big query is running, data spilled has happened because mem_limit was set and this big query waste a lot of memory.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org