[ 
https://issues.apache.org/jira/browse/IMPALA-13130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Smith resolved IMPALA-13130.
------------------------------------
    Fix Version/s: Impala 4.5.0
       Resolution: Fixed

> 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: Major
>             Fix For: Impala 4.5.0
>
>
> 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)

Reply via email to