[
https://issues.apache.org/jira/browse/HIVE-9253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dong Chen updated HIVE-9253:
----------------------------
Attachment: HIVE-9253.2.patch
Thanks very much for your help! [~brocknoland]
I updated the patch V2 with all changes for review. The 3 steps are all done.
1. Implement a threadlocal {{RuntimeTimeout}} class
2. add {{RuntimeTimeout.checkTimeout()}} in HMS code. Added some check in
{{MetaStoreDirectSql}}, which can serve as an example. Since the places needing
check (most are probable in {{ObjectStore}} or {{MetaStoreDirectSql}}) might be
a lot, how about we find them and add checking in a follow-on Jira?
3. Client could reset the timeout value. I found reuse the setMetaConf() api
and add a listener might be ok, instead of creating a new request. This reuse
could avoid adding new interface in HS2 for user to change timeout value.
> MetaStore server should support timeout for long running requests
> -----------------------------------------------------------------
>
> Key: HIVE-9253
> URL: https://issues.apache.org/jira/browse/HIVE-9253
> Project: Hive
> Issue Type: Sub-task
> Components: Metastore
> Reporter: Dong Chen
> Assignee: Dong Chen
> Attachments: HIVE-9253.1.patch, HIVE-9253.2.patch, HIVE-9253.patch
>
>
> In the description of HIVE-7195, one issue is that MetaStore client timeout
> is quite dumb. The client will timeout and the server has no idea the client
> is gone.
> The server should support timeout when the request from client runs a long
> time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
