You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Joe McDonnell (JIRA)" <ji...@apache.org> on 2019/04/30 20:02:00 UTC
[jira] [Updated] (IMPALA-3099) Coordinator::CancelRemoteFragments
should use a thread pool
[ https://issues.apache.org/jira/browse/IMPALA-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe McDonnell updated IMPALA-3099:
----------------------------------
Fix Version/s: Not Applicable
> Coordinator::CancelRemoteFragments should use a thread pool
> -----------------------------------------------------------
>
> Key: IMPALA-3099
> URL: https://issues.apache.org/jira/browse/IMPALA-3099
> Project: IMPALA
> Issue Type: Improvement
> Components: Distributed Exec
> Affects Versions: Impala 2.5.0
> Reporter: Henry Robinson
> Assignee: Joe McDonnell
> Priority: Minor
> Labels: ramp-up
> Fix For: Not Applicable
>
>
> {{Coordinator::CancelRemoteFragments()}} makes one RPC for every fragment instance, serially. There are no dependencies between fragment instances, so we should use {{ExecEnv::rpc_pool()}} to issue the cancellation requests.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org