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

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-23458?focusedWorklogId=572645&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-572645 ]

ASF GitHub Bot logged work on HIVE-23458:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 26/Mar/21 13:06
            Start Date: 26/Mar/21 13:06
    Worklog Time Spent: 10m 
      Work Description: EugeneChung edited a comment on pull request #1919:
URL: https://github.com/apache/hive/pull/1919#issuecomment-782619246


   I don't know why, but when the number of threads is 2, it seems to fail. So I set it to 4. I think 4 is small enough, too.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 572645)
    Time Spent: 1.5h  (was: 1h 20m)

> 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: pull-request-available, todoc4.0
>             Fix For: 4.0.0
>
>         Attachments: HIVE-23458.01.patch, HIVE-23458.02.patch, HIVE-23458.03.patch
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> 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)