[
https://issues.apache.org/jira/browse/HIVE-27172?focusedWorklogId=852892&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-852892
]
ASF GitHub Bot logged work on HIVE-27172:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 24/Mar/23 18:16
Start Date: 24/Mar/23 18:16
Worklog Time Spent: 10m
Work Description: wecharyu opened a new pull request, #4150:
URL: https://github.com/apache/hive/pull/4150
### What changes were proposed in this pull request?
Currently `HiveMetaStoreClient` use `CLIENT_SOCKET_TIMEOUT` as both socket
timeout and connection timeout, we want to introduce a new HiveMetaStoreClient
config for connection timeout:
```java
CLIENT_CONNECTION_TIMEOUT("metastore.client.connection.timeout",
"hive.metastore.client.connection.timeout", 10,
TimeUnit.SECONDS, "MetaStore Client connection timeout in
seconds"),
```
### Why are the changes needed?
1. achieve a more flexible config for client socket timeout and connection
timeout.
2. we can use a smaller connection timeout to fail-fast reconnect to another
HMS server.
### Does this PR introduce _any_ user-facing change?
Yes, user can set the client connection timeout by this conf.
### How was this patch tested?
Add a unit test.
Issue Time Tracking
-------------------
Worklog Id: (was: 852892)
Remaining Estimate: 0h
Time Spent: 10m
> 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
> Time Spent: 10m
> 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)
