You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Fang-Yu Rao (Jira)" <ji...@apache.org> on 2020/01/23 23:00:00 UTC
[jira] [Resolved] (IMPALA-9154) KRPC DataStreamService threads
blocked in PublishFilter
[ https://issues.apache.org/jira/browse/IMPALA-9154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fang-Yu Rao resolved IMPALA-9154.
---------------------------------
Fix Version/s: Impala 3.4.0
Resolution: Fixed
> KRPC DataStreamService threads blocked in PublishFilter
> -------------------------------------------------------
>
> Key: IMPALA-9154
> URL: https://issues.apache.org/jira/browse/IMPALA-9154
> Project: IMPALA
> Issue Type: Bug
> Components: Distributed Exec
> Affects Versions: Impala 3.4.0
> Reporter: Tim Armstrong
> Assignee: Fang-Yu Rao
> Priority: Blocker
> Labels: hang
> Fix For: Impala 3.4.0
>
> Attachments: image-2019-11-13-08-30-27-178.png, pstack-exchange.txt
>
>
> I hit this on primitive_many_fragments when doing a single node perf run:
> {noformat}
> ./bin/single_node_perf_run.py --num_impalads=1 --scale=30 --ninja --workloads=targeted-perf --iterations=5
> {noformat}tan
> I noticed that the query was hung and the execution threads were hung sending row batches. Then looking at the RPCz page, all of the threads were busy:
> !image-2019-11-13-08-30-27-178.png!
> Multiple threads were stuck in UpdateFilter() - see [^pstack-exchange.txt]. It looks like this is a deadlock bug because a KRPC thread is blocked waiting for an RPC that needs to be served by one of the limited threads from that same thread pool
--
This message was sent by Atlassian Jira
(v8.3.4#803005)