[
https://issues.apache.org/jira/browse/HIVE-27172?focusedWorklogId=852901&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-852901
]
ASF GitHub Bot logged work on HIVE-27172:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 24/Mar/23 18:39
Start Date: 24/Mar/23 18:39
Worklog Time Spent: 10m
Work Description: pan3793 commented on code in PR #4150:
URL: https://github.com/apache/hive/pull/4150#discussion_r1147940693
##########
standalone-metastore/metastore-common/src/main/java/org/apache/hadoop/hive/metastore/conf/MetastoreConf.java:
##########
@@ -402,6 +402,8 @@ public enum ConfVars {
"has an infinite lifetime."),
CLIENT_SOCKET_TIMEOUT("metastore.client.socket.timeout",
"hive.metastore.client.socket.timeout", 600,
TimeUnit.SECONDS, "MetaStore Client socket timeout in seconds"),
+ CLIENT_CONNECTION_TIMEOUT("metastore.client.connection.timeout",
"hive.metastore.client.connection.timeout", 10,
Review Comment:
It makes sense to set connection timeout a small value, because generally,
establish the connection is quick, and small timeout make it quick failover if
one HMS is down, but it silent changes the default behavior, I'm not sure if
such change is acceptable in Hive community
Issue Time Tracking
-------------------
Worklog Id: (was: 852901)
Time Spent: 40m (was: 0.5h)
> Add the HMS client connection timeout config
> --------------------------------------------
>
> Key: HIVE-27172
> URL: https://issues.apache.org/jira/browse/HIVE-27172
> Project: Hive
> Issue Type: Task
> Components: Hive
> Reporter: Wechar
> Assignee: Wechar
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently {{HiveMetastoreClient}} use {{CLIENT_SOCKET_TIMEOUT}} as both
> socket timeout and connection timeout, it's not convenient for users to set a
> smaller connection timeout.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
