hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Chung (Jira)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-23458) Introduce unified thread pool for scheduled jobs
Date Thu, 14 May 2020 13:32:00 GMT

     [ https://issues.apache.org/jira/browse/HIVE-23458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Eugene Chung updated HIVE-23458:
--------------------------------
    Attachment: HIVE-23458.02.patch
        Status: Patch Available  (was: Open)

 [^HIVE-23458.02.patch] The license comment is added.

> Introduce unified thread pool for scheduled jobs
> ------------------------------------------------
>
>                 Key: HIVE-23458
>                 URL: https://issues.apache.org/jira/browse/HIVE-23458
>             Project: Hive
>          Issue Type: Improvement
>          Components: HiveServer2
>            Reporter: Eugene Chung
>            Assignee: Eugene Chung
>            Priority: Major
>              Labels: todoc4.0
>             Fix For: 4.0.0
>
>         Attachments: HIVE-23458.01.patch, HIVE-23458.02.patch
>
>
> As I mentioned in [the comment of HIVE-23164|https://issues.apache.org/jira/browse/HIVE-23164?focusedCommentId=17089506&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17089506],
I've made the unified scheduled executor service like org.apache.hadoop.hive.metastore.ThreadPool.
> I think it could help
> 1. to minimize the possibility of making non-daemon threads when developers need ScheduledExecutorService
> 2. to achieve the utilization of server resources because the current situation is all
of the modules make its own ScheduledExecutorService and all of the threads are just using
for one job. 
> 3. administrators of Hive servers by providing hive.exec.scheduler.num.threads configuration
so that they can predict and set how many threads are used and needed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message