You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Sailesh Mukil (JIRA)" <ji...@apache.org> on 2017/10/23 19:06:00 UTC
[jira] [Created] (IMPALA-6101) DataStreamMgr::Cancel() should take
a query ID instead of a finst ID
Sailesh Mukil created IMPALA-6101:
-------------------------------------
Summary: DataStreamMgr::Cancel() should take a query ID instead of a finst ID
Key: IMPALA-6101
URL: https://issues.apache.org/jira/browse/IMPALA-6101
Project: IMPALA
Issue Type: Improvement
Components: Distributed Exec
Affects Versions: Impala 2.10.0
Reporter: Sailesh Mukil
Currently our DataStreamMgr class is a singleton class, which means it has a holistic view of all fragment instances running on a given impalad node.
We currently call DataStreamMgr::Cancel() per fragment instance, which means on every Cancel() call, we do a O(N) lookup through a receiver map maintained by the DataStreamMgr, even though we know that if one fragment instance belonging to a query is cancelled, all other fragment instances belonging to that query will be cancelled as well.
Instead, if we take a query ID, we can cancel all fragment instances belonging to that query at once, with a single O(N) lookup of the receiver map.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)