[
https://issues.apache.org/jira/browse/IMPALA-10578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17302306#comment-17302306
]
Quanlong Huang commented on IMPALA-10578:
-----------------------------------------
[~wesleydeng] Could you upload the profiles of both of the queries?
> 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
> Priority: Major
> Attachments: image-2021-03-10-19-59-24-188.png
>
>
> When a big query is running(use mt_dop=8), other query is very difficult to
> start.
> A small query (select distinct one field from a small table) may take about
> 1 minutes, normallly it take only about 1~3 second.
> 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|width=768,height=180!
> !image-2021-03-10-19-59-24-188.png|width=892,height=435!
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
