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 "Quanlong Huang (Jira)" <ji...@apache.org> on 2024/08/14 00:50:00 UTC
[jira] [Commented] (IMPALA-13130) Under heavy load, Impala does not prioritize data stream operations
[ https://issues.apache.org/jira/browse/IMPALA-13130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873364#comment-17873364 ]
Quanlong Huang commented on IMPALA-13130:
-----------------------------------------
Backported to branch-4.4.1 as commit bb9df269a
> Under heavy load, Impala does not prioritize data stream operations
> -------------------------------------------------------------------
>
> Key: IMPALA-13130
> URL: https://issues.apache.org/jira/browse/IMPALA-13130
> Project: IMPALA
> Issue Type: Bug
> Reporter: Michael Smith
> Assignee: Michael Smith
> Priority: Critical
> Fix For: Impala 4.5.0, Impala 4.4.1
>
>
> Under heavy load - where Impala reaches max memory for the DataStreamService and applies backpressure via https://github.com/apache/impala/blob/4.4.0/be/src/rpc/impala-service-pool.cc#L191-L199 - DataStreamService does not differentiate between types of requests and may reject requests that could help reduce load.
> The DataStreamService deals with TransmitData, PublishFilter, UpdateFilter, UpdateFilterFromRemote, and EndDataStream. It seems like we should prioritize completing EndDataStream, especially under heavy load, to complete work and release resources more quickly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org