[ 
https://issues.apache.org/jira/browse/HIVE-7140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026082#comment-14026082
 ] 

Lefty Leverenz commented on HIVE-7140:
--------------------------------------

Good question, [~brocknoland].  We've used release notes for doc tasks 
previously, and that seems better than labels.  To make it work we should have 
a standard phrase which everyone remembers to use, but I'm not confident about 
compliance so I've been flagging email messages "to-doc-14" in gmail for a 
personal list.

Hm, TO-DOC-14 might be a good phrase for the release notes.

Another approach would be to create a Jira ticket where we can list release 
0.14's doc tasks in the comments.  That seems unnecessarily complicated, 
though.  Do you have any other suggestions?

I'll try to find the previous discussion on this topic.  [~thejas] was a 
participant, as I recall.

> Bump default hive.metastore.client.socket.timeout to 5 minutes
> --------------------------------------------------------------
>
>                 Key: HIVE-7140
>                 URL: https://issues.apache.org/jira/browse/HIVE-7140
>             Project: Hive
>          Issue Type: Improvement
>    Affects Versions: 0.10.0, 0.12.0, 0.13.0
>            Reporter: Brock Noland
>            Assignee: Brock Noland
>             Fix For: 0.14.0
>
>         Attachments: HIVE-7140.patch
>
>
> The issue is that OOTB clients often face timeouts when using HMS since many 
> operations in the HMS completes are long running (e.g. many operations on a 
> table with many partitions). A few supporting pieces of information:
> * The default value of hive.metastore.client.socket.timeout is 20 seconds.
> * Since the timeout is client only, the server happy continues doing the 
> requested work
> * Clients retry after a small delay to perform the requested work again, 
> often while the server is still trying to complete the original request
> * A few tests have actually increased this value in order to pass reliably.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to