You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Eugene Chung (Jira)" <ji...@apache.org> on 2020/05/13 07:03:00 UTC

[jira] [Updated] (HIVE-23458) Introduce unified thread pool for scheduled jobs

     [ 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.01.patch
        Status: Patch Available  (was: Open)

> 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
>         Attachments: HIVE-23458.01.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. an administrator of Hive server by providing hive.exec.scheduler.num.threads configuration.



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