You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Vihang Karajgaonkar (Jira)" <ji...@apache.org> on 2020/12/23 18:05:00 UTC
[jira] [Resolved] (IMPALA-9140) Get rid of the unnecessary load
submitter thread pool in tblLoadingMgr
[ https://issues.apache.org/jira/browse/IMPALA-9140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vihang Karajgaonkar resolved IMPALA-9140.
-----------------------------------------
Resolution: Won't Fix
Based on the discussion above, it looks like there is no significant benefit by fixing this JIRA. Closing this as "won't fix".
> Get rid of the unnecessary load submitter thread pool in tblLoadingMgr
> ----------------------------------------------------------------------
>
> Key: IMPALA-9140
> URL: https://issues.apache.org/jira/browse/IMPALA-9140
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
> Reporter: Vihang Karajgaonkar
> Priority: Major
>
> This JIRA is created as a followup on the discussion on https://gerrit.cloudera.org/#/c/14611 related to various pools used for loading tables.
> It looks like there are 2 pools of threads both of the size {{num_metadata_loading_threads}}. One pool is used to submit the load requests to another pool {{tblLoadingPool_}} which does the actual loading of the tables. I think we can get rid of the pool which submits the tasks since it is not very time-consuming operation and can be done synchronously (all it needs to do submit the task in the queue in the front or back based on whether its a prioritized load or background load). This will simplify the loading code and reduce unnecessary number of threads being created by {{TblLoadingMgr}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)