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

Jaume M updated HIVE-20936:
---------------------------
    Attachment: HIVE-20936.17.patch
        Status: Patch Available  (was: Open)

> Allow the Worker thread in the metastore to run outside of it
> -------------------------------------------------------------
>
>                 Key: HIVE-20936
>                 URL: https://issues.apache.org/jira/browse/HIVE-20936
>             Project: Hive
>          Issue Type: Improvement
>          Components: Transactions
>            Reporter: Jaume M
>            Assignee: Jaume M
>            Priority: Major
>         Attachments: HIVE-20936.1.patch, HIVE-20936.10.patch, 
> HIVE-20936.11.patch, HIVE-20936.12.patch, HIVE-20936.13.patch, 
> HIVE-20936.14.patch, HIVE-20936.15.patch, HIVE-20936.16.patch, 
> HIVE-20936.17.patch, HIVE-20936.2.patch, HIVE-20936.3.patch, 
> HIVE-20936.4.patch, HIVE-20936.5.patch, HIVE-20936.6.patch, 
> HIVE-20936.7.patch, HIVE-20936.8.patch, HIVE-20936.8.patch
>
>
> Currently the Worker thread in the metastore in bounded to the metastore, 
> mainly because of the TxnHandler that it has. This thread runs some map 
> reduce jobs which may not only be an option wherever the metastore is 
> running. A solution for this can be to run this thread in HS2 depending on a 
> flag.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to