[
https://issues.apache.org/jira/browse/IMPALA-12300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Riza Suminto resolved IMPALA-12300.
-----------------------------------
Target Version: Impala 4.3.0
Resolution: Fixed
> Turn Scheduler::CheckEffectiveInstanceCount to print warning
> -------------------------------------------------------------
>
> Key: IMPALA-12300
> URL: https://issues.apache.org/jira/browse/IMPALA-12300
> Project: IMPALA
> Issue Type: Improvement
> Reporter: Riza Suminto
> Assignee: Riza Suminto
> Priority: Major
>
> Scheduler::CheckEffectiveInstanceCount was added to check consistency between
> FE planning and BE scheduling if COMPUTE_PROCESSING_COST=true. This
> consistency can be broken if there is a cluster membership change (new
> executor becomes online) between FE planning and BE scheduling. Say, in
> executor group size 10 with 90% health threshold, admission-controller is
> allowed to run a query when only 9 executor is available. If 10th executor is
> online during BE scheduling, CheckEffectiveInstanceCount can fail and return
> error.
> It should be OK to turn this error form CheckEffectiveInstanceCount into
> warning since query plan for fewer executor should generally OK to run in
> larger executor group size.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
