[
https://issues.apache.org/jira/browse/IMPALA-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155623#comment-17155623
]
ASF subversion and git services commented on IMPALA-3380:
---------------------------------------------------------
Commit 17b083d371c8e62c30a5cc7fe6c4aa474866f289 in impala's branch
refs/heads/master from Sahil Takiar
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=17b083d ]
IMPALA-3380: Add a timeout for statestore RPCs
Adds the following startup flags for statestore subscribers:
'statestore_client_rpc_timeout_ms'. The timeout is set to 5 minutes by
default.
Testing:
* Adds some tests for catalog_client_rpc_timeout_ms that validate the
timeout is used correctly, and that retries are triggered
Change-Id: If49892ff1950cf474f951aabf4c952dbc44189e2
Reviewed-on: http://gerrit.cloudera.org:8080/16150
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Add TCP timeouts to all RPCs that don't block
> ---------------------------------------------
>
> Key: IMPALA-3380
> URL: https://issues.apache.org/jira/browse/IMPALA-3380
> Project: IMPALA
> Issue Type: Sub-task
> Components: Distributed Exec
> Affects Versions: Impala 2.5.0
> Reporter: Henry Robinson
> Assignee: Sahil Takiar
> Priority: Minor
> Labels: observability, supportability
>
> Most RPCs should not take an unbounded amount of time to complete (the
> exception is {{TransmitData()}}, but that may also change). To handle hang
> failures on the remote machine, we should add timeouts to every RPC (so,
> really, every RPC client), and handle the timeout failure.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
