[
https://issues.apache.org/jira/browse/IMPALA-10599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17305838#comment-17305838
]
Quanlong Huang commented on IMPALA-10599:
-----------------------------------------
I think "exception nodes" in the title means busy nodes, e.g. cpu usage reach
100% but just causing query slowness. We want to skip scheduling fragment
instances to these nodes until their resource usage come down.
If these nodes can cause query failures, after IMPALA-9299 is resolved,
coordinator can add them into blacklist and never use them anymore.
> The coordinator should avoid distributing query fragments to exception nodes.
> -----------------------------------------------------------------------------
>
> Key: IMPALA-10599
> URL: https://issues.apache.org/jira/browse/IMPALA-10599
> Project: IMPALA
> Issue Type: Improvement
> Components: Distributed Exec
> Affects Versions: Impala 3.2.0, Impala 3.4.0
> Environment: LSB Version: core-4.1-amd64
> Distributor ID: CentOS
> Description: CentOS release 7.4.1708.7
> Release: 7.4.1708.7
> impala version: 3.2.0
> Reporter: zhi tang
> Priority: Major
> Labels: features
>
> When I join[shuffle] with unbalanced fields, there will be data-skewed nodes
> during execution.This will result in the skewed node being under high load
> for a long time, because the query is likely to be endless.If other queries
> are committed or running during this time, they may be rejected or an
> exception thrown.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
