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 "Bikramjeet Vig (Jira)" <ji...@apache.org> on 2019/09/05 18:22:00 UTC
[jira] [Resolved] (IMPALA-8791) Handle the case where there is no
fragment scheduled on the coordinator for a query
[ https://issues.apache.org/jira/browse/IMPALA-8791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bikramjeet Vig resolved IMPALA-8791.
------------------------------------
Fix Version/s: Impala 3.4.0
Resolution: Fixed
> Handle the case where there is no fragment scheduled on the coordinator for a query
> -----------------------------------------------------------------------------------
>
> Key: IMPALA-8791
> URL: https://issues.apache.org/jira/browse/IMPALA-8791
> Project: IMPALA
> Issue Type: Bug
> Affects Versions: Product Backlog
> Reporter: Bikramjeet Vig
> Assignee: Bikramjeet Vig
> Priority: Major
> Fix For: Impala 3.4.0
>
>
> For insert statements executed on a dedicated coord, the fragments get schduled only on executors but a query state object still gets started up on the coord host with the coord_mem_limit. we end up with a situation where the mem admitted is zero for the coord but the mem_reserved is non-zero which would affect other admission decisions.
> There is also a case where there is no coordinator fragment but the execution fragment gets scheduled on the coord (eg. insert into <tbl> values....) for this case, the mem admitted is per_backend_mem_limit_ but the mem limit applied to the coord query state is coord_backend_mem_limit_ which again causes a inconsistency.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org