[
https://issues.apache.org/jira/browse/IMPALA-13427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wenzhe Zhou resolved IMPALA-13427.
----------------------------------
Fix Version/s: Impala 4.5.0
Resolution: Fixed
> Make the statestore HA rpc's socket connection timeout tunable
> --------------------------------------------------------------
>
> Key: IMPALA-13427
> URL: https://issues.apache.org/jira/browse/IMPALA-13427
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Reporter: Wenzhe Zhou
> Assignee: Wenzhe Zhou
> Priority: Major
> Fix For: Impala 4.5.0
>
>
> In some deployment environment, unsuccessful socket connection attempts take
> long time to return error if connTimeout of the socket is set as 0. This
> causes a daemon to tie up in unsuccessful connection attempts during
> initialization if its peer is not ready.
> When statestored HA is enabled, statestoreds do HA hand shack to negotiate
> active role during initialization. If two statestored are initialized
> serially, the first statestored may tie up in unsuccessful connection
> attempts since the second statestored is not started.
> Currently socket connection timeout of Thrift RPC is always set as 0. To
> avoid this issue, we need to make the statestore HA rpc's socket connection
> timeout tunable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
