[
https://issues.apache.org/jira/browse/IMPALA-12300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747082#comment-17747082
]
ASF subversion and git services commented on IMPALA-12300:
----------------------------------------------------------
Commit 0d3fc33bbbe8313788547d30b507a0b0effc4951 in impala's branch
refs/heads/master from Riza Suminto
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=0d3fc33bb ]
IMPALA-12300: (addendum) Remove HDFS specific assertion
test_75_percent_availability fail against Ozone and S3 test environment
because test expects the string "SCAN HDFS" to be found in the profile.
Instead of it there's "SCAN OZONE" and "SCAN S3" for Ozone and S3 test
environment respectively. This patch fix the test by removing that
assertion from test_75_percent_availability. The remaining assertion is
enough to verify that FE planner and BE scheduler can see cluster
membership change.
Change-Id: Id14934d2fce0f6cf03242c36c0142bc697b4180e
Reviewed-on: http://gerrit.cloudera.org:8080/20259
Reviewed-by: Wenzhe Zhou <[email protected]>
Reviewed-by: Michael Smith <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
